BIND 10 #2619: getFullConfig() does not do what you'd think it does
BIND 10 Development
do-not-reply at isc.org
Wed Jan 9 18:51:04 UTC 2013
#2619: getFullConfig() does not do what you'd think it does
-------------------------------------+-------------------------------------
Reporter: jelte | Owner: jelte
Type: defect | Status:
Priority: medium | reviewing
Component: Unclassified | Milestone:
Keywords: | Sprint-DHCP-20130122
Sensitive: 0 | Resolution:
Sub-Project: DNS | CVSS Scoring:
Estimated Difficulty: 0 | Defect Severity: N/A
Total Hours: 0 | Feature Depending on Ticket:
| Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by stephen):
* owner: stephen => jelte
Comment:
Reviewed commit 397592d08bdf50867607aac57cae5aef6ccf9c61
That does the trick, thanks.
The code can be merged. However, this ticket has been branched from #2559.
To keep things clear (plus the fact that #2559 is not yet complete), I'd
suggest merging these changes separately to master. I need to merge
master into #2559 anyway to pick up some other changes, so will be able to
use this modification in further development and testing.
I would also suggest that this alteration needs a !ChangeLog entry -
perhaps something like:
{{{
NNN. [func] jelte
When sending a full configuration to BIND 10 modules, the
configuration is now
set as properly-structured JSON. Previously, the structure had
been flattened,
with all data being labelled by fully-qualified element names.
(Trac #2619, git xxx)
}}}
--
Ticket URL: <http://bind10.isc.org/ticket/2619#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list