Variables in the Process that Don't Exist in the Scope

When a variable is being used in the process that doesn’t exist in the scope, meaning there isn’t a variable for that specific environment and/or tag for that variable, is there any way to throw an exception? Right now, it fails silently by just using “#{variable}” in the process which is never helpful.

Just to give an example, I had AppPoolUser defined for a low level environment but not for the next level up. When I moved to the next environment in the stack, #{AppPoolUser} was used as the username for the app pool and the deployment ran as a success. Obviously, my website disagreed with that since it’s app pool was running as a non-existent user.


Thanks for getting in touch. We’re planning some work in this area shortly - I created a fresh ticket with details:


Nice, thanks!