BIND 10 #1707: Default configuration was used when mistake in different configuration

[BIND 10 Development]

#1707: Default configuration was used when mistake in different configuration
-------------------------------------+-------------------------------------
                   Reporter:  jreed  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:
                   Priority:         |  Sprint-20120403
  medium                             |            Resolution:
                  Component:         |             Sensitive:  0
  b10-auth                           |           Sub-Project:  DNS
                   Keywords:         |  Estimated Difficulty:  4
            Defect Severity:  Very   |           Total Hours:  0
  High                               |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 I've looked into it, and I think I understood how this happened.

 When b10-auth constructs `ModuleCCSession`, the latter retrieves the
 config spec and its default, and passes it to b10-auth via the
 callback.  b10-auth first tries to install the given configuration,
 and then it calls ModuleCCSession::getFullConfig() to get the merged
 full configuration (defaults with overridden local config), and
 installs it.

 When the first attempt fails, the local configuration is considered
 empty, and b10-auth is given default-only configuration and installs
 it.  Note that even if the first installation succeeds, it's not an
 ideal scenario in that the same configuration data need to be
 installed again.

 I can think of some minimalist hack to fix this problem, but I suspect
 it suggests that it's time to solve various configuration related
 issues at a higher level, maybe also revisiting APIs.  We know many
 small issues related to configuration and many of them were deferred
 due to various reasons including time constraints.  But now that we
 are going to focus on usability, I think we should start solving these
 issues in a higher level context.

 Maybe we should discuss this at bind10-dev?

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