Stop overwriting the routes.yaml file

[cprice404]

The current implementation of this module overwrite routes.yaml with the exact settings needed by PuppetDB. If a user already has a routes.yaml file that is managing other things besides the the facts terminus, their settings will be blown away.

We should handle this more gracefully. It ought to be pretty simple to put together a yaml module that had a resource type for dealing with an individual yaml setting. If we did that, then the PuppetDB module could use that to set only the relevant settings without overriding any existing settings.

[branan]

I think that a type which is specific to routes.yaml would be more user-friendly than a generic yaml module.

[cprice404]

True. The former could be built on top of the latter, though.