[XML .config refactoring plans] Refactor the XML .config file handling by changing the config that comes with the file instead of using chef templates #chef #template #config #xml

planning.md

XML .config Handling

Why

If we don't rely on each cookbook holding the correct configuration file, we become more version agnostic than we could be previously

How

Write either a powershell/ruby script or custom resource that will allow for specifying an XML key and the intended value

When

Not yet