Our applications deployed via Octopus contain configuration variables that are dates and require updating periodically. We have implemented the dates as Octopus variables that transform the configs at deployment, which works fine.
The fact that we have dates in our configs is a legacy issue that cannot be avoided for now.
But, we need to be able to handle updating these values and how to get these new values deployed to our servers. We would like to avoid having re-deploy applications every time we want to update the configuration. To keep everything source controlled and in sync we want to avoid users manually updating files, as these values would then get out of sync with the Octopus variables.
Is there any way to get an Octopus deployment to just re-deploy config files to an existing deployment?