Variable replacement question

Is it possible to specify the environment when doing variable substitution?

So instead of #{Foo}, it might be handy to specify #{Env2::Foo}.


Hi Scott,

No, it’s not possible. Can you explain the scenario a bit more? Variables can be scoped to environments - when deploying to Prod, “#{Foo}” will resolve to the production value.


We have one Web app that actually uses sql connect strings from multiple environments (dev,beta,prod). Currently, I handle it all in xml transform files via xml replacements with hard coded connect strings (no variable substitution). These sql connect strings happen to also be defined by environment using Octopus variable sets. Might be cool if you could optionally specify the environment name in the Octopus variable for the occasional scenario where one project needs to span environment variables. Maybe something like: