BIND 10 #918: Non-dict top-level configuration

[BIND 10 Development]

#918: Non-dict top-level configuration
-------------------------------------+-------------------------------------
            Reporter:  vorner        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:                |  Tasks
  configuration                      |                     Keywords:
           Sensitive:  0             |              Defect Severity:  N/A
         Sub-Project:  Core          |  Feature Depending on Ticket:
Estimated Difficulty:  0             |          Add Hours to Ticket:  0
         Total Hours:  0             |                    Internal?:  0
-------------------------------------+-------------------------------------
 Currently a module configuration must be a dict and with names hardcoded
 in the spec file (eg. we say that we'll have
 module.a, module.b and that's it). These items can have any type then.

 But for process-less configurations, it makes sense to have a different
 type for the whole module. An example would be
 tsig_keys configuration section, which would be shared between multiple
 processes. It would make sense for it to be
 just list of strings, each representing one TSIG key in the keyring.
 Current workaround in #875 is to put there one more
 level, but it's inconvenient for the user.

 (I'm putting it to core, as the configuration is shared)

-- 
Ticket URL: <http://bind10.isc.org/ticket/918>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development