BIND 10 #2025: system test for notify

[BIND 10 Development]

#2025: system test for notify
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  high   |  Sprint-20120703
                  Component:  xfrin  |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DNS
Feature Depending on Ticket:         |  Estimated Difficulty:  5
        Add Hours to Ticket:  0      |           Total Hours:  0
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => vorner


Comment:

 Replying to [comment:11 vorner]:
 > Well, I understand the reason and the meaning of the configuration
 variable. And that is exactly what I don't like ‒ having user-facing
 configuration that should not be used.
 >
 > The `also_notify` is something a user might want to use when they need
 to send notifies to addresses not listed in the NS records. It seems to me
 this is exactly the same feature. So I propose to rename it to also-
 notify, make a note about it to #1992 and put it to next-sprint-proposed
 to add tests for it. Would that be OK with you?

 I've updated the key to `also_notify` now, though it's still limited to
 just `address` and `port` keys. Also did some minor cleanup. Will update
 #1992 when it hits master.

-- 
Ticket URL: <http://bind10.isc.org/ticket/2025#comment:12>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development