BIND 10 #472: unknown configuration in b10-config.db causes rest of per-module configuration to be ignored

[BIND 10 Development]

#472: unknown configuration in b10-config.db causes rest of per-module
configuration to be ignored
--------------------------------+-------------------------------------------
      Reporter:  jreed          |        Owner:  jelte
          Type:  defect         |       Status:  new  
      Priority:  major          |    Milestone:       
     Component:  configuration  |   Resolution:       
      Keywords:                 |    Sensitive:  0    
Estimatedhours:  0.0            |        Hours:  0    
      Billable:  1              |   Totalhours:  0    
      Internal:  0              |  
--------------------------------+-------------------------------------------

Comment(by jelte):

 Hmm. So it's not that other modules don't get their respective
 configurations, it's boss that doesn't understand its own (and falls back
 to a default, and hence starts the wrong ones).

 In order to handle this, we need to either have per-module versioning of
 config data (and have modules handle updating), or we could simply have
 boss stop if it doesn't recognize what it gets.

 Or we could have boss just exit if it doesn't understand its initial
 configuration :)

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