* Zone object no longer treats them special, some tests needed adjusting
b/c of this, some provider's tests may also need adjusting, though
they should not plan changes since they won't (yet) have
SUPPORTS_ROOT_NS
* _process_desired_zone filters and warns when not supported
* YamlProvider supports them
* TinyDnsBaseSource supports them
The SplitYamlProvider itself now requires a directory matching the
zone name under its directory to contain all YAML files. This doesn't
actually change the intended usage at all, just how the configuration
file is laid out.
Signed-off-by: Christian Funkhouser <cfunkhouser@heroku.com>
SplitYamlProvider extends and behaves similarly to YamlProvider, but
organizes the zone in multiple files by record, insteat of in a
monolithic YAML file.
YamlProvider has been slightly modified to make its extension easier.
Signed-off-by: Christian Funkhouser <cfunkhouser@heroku.com>
- adds lenient flag to Record.new, problems during validation are just
warnings if it's true
- target populate calls during the plan phase pass lenient=True
- make all of the provider.populate call logging consistent including both
target and lenient
- add source=self to Record.new in a few places that were missing it
