Decorate overridden config file settings with an Octopus tag (or something)
Some of our services have large config files and we will allow some settings to be defaulted (not configured through the Octopus UI) and others must be configured. I would like a Project Level setting to be included that if enabled would decorate the deployed config file with some indication that Octopus overrode the setting. This would help tremendously to be sure which settings were defaulted and which were set by Octopus.
Nick Greiner
shared this idea
-
dragon788
commented
This sounds like you are expecting to look at the server and be able to figure out the current software state, this isn't a great assumption because if you have access to the server, so might somebody else, and those Octopus tags would be useless if you are letting people access the Web.config. Your best bet is to examine the Octopus Deploy overview to see which release is currently deployed, and then examine the deployment log in Verbose mode to view which variables were updated in which locations. Since this can be dozens of files, adding tags for every replace in every file could very well increase the total size and duration of a deployment a significant amount, multiplied by every deploy that happens on a regular basis.