Hi. I’m using Octopus 2019.6.0.
I have found that if a default value is set for a “prompt for value” for a variable, and then add a duplicate variable or additional value is added which should take precedence according to scoping rules, the latter is ignored in deployments and the default value from the prompt variable is taken.
examples seen so far:
- ‘Prompt for value’ for environment X with default of ‘true’ and non-prompt of “False” for environment Y leads to working value of “True” in environment Y
- Prompt for value in library variable set with default value of ‘true’ and non-prompt of “False” (to override) for a specific project which uses the library set, leads to working value of “True” for the project.
Haven’t checked to see if the behaviour is the same if the override value is also a prompt variable, but really it shouldn’t matter. The user might, in general, want to prompt, but if they decide for a specific situation to always use the same but different value, then they are stuck with original default