BIND 10 #2113: Configuration plugin check for datasources

[BIND 10 Development]

#2113: Configuration plugin check for datasources
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jelte
  vorner                             |                Status:  reviewing
                       Type:         |             Milestone:
  defect                             |  Sprint-20120807
                   Priority:         |            Resolution:
  medium                             |             Sensitive:  0
                  Component:         |           Sub-Project:  DNS
  configuration                      |  Estimated Difficulty:  5
                   Keywords:         |           Total Hours:  0
            Defect Severity:  N/A    |
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by vorner):

 * owner:  vorner => jelte


Comment:

 Hello

 Replying to [comment:8 jelte]:
 > Replying to [comment:7 vorner]:
 > > So, what do we do about the warning? I probably could mangle the
 configuration to not contain the zones and check them manually only. Would
 that be OK or does it sounds like too much of a hack?
 >
 > I was about to say that i'd prefer some form of 'dry run', where
 everything is checked but not actually loaded. But I guess that is the
 whole purpose of the config plugin in the first place.

 Yes, that's the dry run ;-). Well, it assumes most data sources are just
 databases and they are cheap to initialize.

 > Since masterfiles is already treated as a special case, could we just
 check whether the files exist and are readable (and not pass it to
 configure() if type is masterfiles)? Masterfiles is already special-cased
 in both the checker plugin and the client list.

 Well, that's mostly what I meant by the hack. I do pass the data source
 there, for two reasons:
  * It is easier to replace the parameters than remove the element from the
 list
  * It still can check other parameters, if there ever are more general
 ones (like cache parameters, or something)

-- 
Ticket URL: <https://bind10.isc.org/ticket/2113#comment:9>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development