Settings and activity
5 results found
-
2 votes
Emil shared this idea ·
-
20 votes
An error occurred while saving the comment -
16 votes
Emil supported this idea ·
-
3 votes
Emil supported this idea ·
-
6 votes
Emil supported this idea ·
An error occurred while saving the comment Emil commented
I guess this could be extended to something like "Variable Policy" for example:
- all variables available in one environment must be identical in this environment
- use all variables from another environment i.e. if a variable is not available in current environment try to resolve it from another environmentThe use case here is to apply "Variable Policy" rules in Pre-Prod & PROD environments to stop false "green" releases with missing or incorrect variable values. For example we can fully test releases in Pre-Prod but cannot test in PROD and the variables setup is manual step with high risk!
I guess the current implementation of DryRun will solve the problem of what happens of variables for a particular target environment :)
https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/6169634--dry-run-deployment
I need to examine the content of the artifact, however calling the API after creation even with a delay does not seem to work so having a cmdlet will be great!