You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 27, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/enhancementThis issue represents an enhancement we are committed to adding to Octopus as some time
Once, using an undefined variable like
#{Fooo}
would cause an error. On moving to 2.0, since we now use partially-evaluated variables in many more places, this is no longer an error - which for users is less convenient than the old fail-fast approach was: http://help.octopusdeploy.com/discussions/questions/2077-variables-in-the-process-that-dont-exist-in-the-scopeThe root issue here is that the original variable evaluator works on a set at a time.
Variable evaluation should be completely lazy/dynamic, so that undefined variables are fine so long as they're not used, but if used they throw.
The text was updated successfully, but these errors were encountered: