I have recently had tickets raised from our Live deployment people stating that their prompted variables are not the answers they were expecting.
When I look at the setup we have a prompted variable with a value and no scope, in this instance set to “false”, then a second value, not prompted and a value of “true”, but scoped to an Environment. This would be production, but in the test example screens below, our scope will be “charlie”.
When choosing to deploy to the Bravo environment, the prompt displays as “false” as expected:
When choosing to deploy to the Charlie environment, the prompt displays as “false”, however we were expecting it to be “true”:
If I make both variable values to be prompted, I see two checkboxes when coming to deploy (was not expecting to see two), and I get one “false”, and one as “true”! Although having both shown to the user would be confusing, so doubt this is an acceptable solution:
I have searched the forum and read this article:
Which indicates it should be reading the variable scopes correctly, however due to my testing of one variable, it feels like I would need to find all of our Prompted Variables and we would have to scope all of the “defaults” to be all the ‘other’ environments. Which will be one hell of a task!
Is this expected functionality? I am certain this used to work and I’m wondering if something has been changed?
I updated us to be using the latest version yesterday (Octopus.2023.2.13151-x64), just in case it was a version thing, but it has not resolved the issue.
Thanks for any help or things to try