We are testing Octopus Deploy to see if it matches our needs and after using the solution for some time we couldn’t find a way to exclude some .config files when the transformer does its magic, Octopus deploy complains about some of our non transformable config file.
Is there any way to go about solving this please.
Thanks for getting in touch! If you have the configuration files features turned on, Octopus will look for the generic config file names and try to transform them.
There is no way to exclude these files from an attempted transform if they are found and that feature is turned on.
I managed a work around that renames the extension before deployment and returns the extension after, We will work that for now.