Split out config file variable replacement so that it can be called external to Octopus
We are using TeamCity as a CI engine, and trigggering OD from there. Once we have triggered a deployment, we want to run tests against that environment.
At present, we need to have the required configuration settings in both OD and the code to allow the tests to point to this environment.
We can currently use the api to get the variable values from a release, and duplicate the code from Octopus to update a config file, however this will be a maintenance nightmare as Octopus evolves.
It would be great if there was a way to use Octopus to apply the transformation.
5
votes
