When the am-config-upgrader tool is run against a directory which contains a subset of the full am FBC config files it generates new files.
This issue affects FRaaS as we do not commit to Git any am config files which keep their default values.
- Obtain a directory of partial config (such as the FRaaS express am config)
- Run the am-config-upgrader against this directory of config
- Observe that the resulting changes include the introduction of new config files
When run manually I have removed all created files. However, this runs the risk of accidentally deleting one or more files which are actually needed.