Currently we perform CMDB upgrades using our bash based executor and have assumed that any other executor should implement them as well.
This blurs the line between our idea of splitting the engine from the executor #1231 apart, with the CMDB owned by the engine and the executor using the engine as an API to the CMDB
This ticket is to move the existing CMDB management tasks ( cmdb upgrades and cmdb cleanups ) into our freemarker based engine.
This will require write access to the CMDB to perform these tasks
The act of upgrading should also be separated from the generation of templates. The generation should check for version compatibility and point to an upgrade if things aren't compatible.
Currently we perform CMDB upgrades using our bash based executor and have assumed that any other executor should implement them as well.
This blurs the line between our idea of splitting the engine from the executor #1231 apart, with the CMDB owned by the engine and the executor using the engine as an API to the CMDB
This ticket is to move the existing CMDB management tasks ( cmdb upgrades and cmdb cleanups ) into our freemarker based engine.
This will require write access to the CMDB to perform these tasks