'Dry Run' Deployment
Sometimes deployments are bad due to bad configuration variables that are un-testable before releasing to production.
Having the ability to 'dry run' a deployment and see all the task outputs with specific highlighting for variables and evaluated variables would allow the identification of changes that need to be made before actually deploying to an environment.
Work has begin on providing a tool to evaluate variables before deployment
At the moment we don’t have further plans to apply config transforms before a release but this should help solve the bigger question of “what will my all my variable values actually be at run time”
Anders Truelsen commented
Show variables in the Release dialog does not evaluate the variables to their actual values.
Eg. if one variable uses one or more variables to produce its value the final value is not shown.
This would make up for not having "dry run".
Adam Bezverkov commented
If all this feature did was show the evaluated variables, transforms, and variable substitutions it would still be immensely helpful!
This would be an extremely valuable functionality as a growing number of variables and incresed complexity due to transformations and combinations of input, results in a lot of calculated variables.
It will take hours to find out if we have configured correctly for all environments, but Octopus will be able to evaluate them in seconds.