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”
An error occurred while saving the commentMichael Christensen commented
If you have a setup with a lot of variables targeting different steps/roles/environments, it becomes difficult to predict what the exact variable values delivered to each step will be.
For instance, I might have forgotten to define an important variable scoped for our production environment. My deployment script will then fail because the value is missing.
It would cut down on the deployment error rate if it was possible to ask a release to show the variables that would be available in each of the steps associated with it, given an environment.
A nice to have would be to be able to compare which variables are available to the same step in the different environments side-by-side, to spot variables available to only a subset of the environmentsMichael Christensen supported this idea ·
5 votesMichael Christensen shared this idea ·