Unexpected Variable Resolution Behavior


We have discovered that Octopus will automatically pick a value for a variable during a process step when the resolution of that variable is ambiguous. Is there a way to configure the server to fail the step if the variable resolution is ambiguous, or there is no matching variable at all?


Hi @mcopeland,

Thank you for contacting Octopus Support.

The variable should remain unevaluated if there isn’t a valid scoping against the target. One scenario to watch out for is when a Process Step is scope to a Role but the Target has additional Roles as well. We have a recent GitHub issue on this as the Variable Preview can be misleading.

I can think of two options for failing that may work for you. First, you can use Variable Run Conditions that will only allow a Step to run when the variable expression evaluates to true. The other option would be to add a script Step to the Process that compares the evaluated variable value against a list of acceptable values.

If you have any additional questions, please don’t hesitate to ask.

Best Regards,

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.