That would be a neat magic variable. It's likely we do support the regular pipeline variables in those spots, but just so I can be sure can you upload an image of the pipeline step where you're setting "Git Repo Branch" or Ref Type -> "RefValue" form fields.

This would be better handled through stacks given that stacks allow variables anywhere within the yaml/json. Gives the max amount of flexibility, allows you to manage multiple images/containers at one time, and enables an "environments as code" approach.

Environments as code is similar to Infrastructure as Code (IaC) but decouples the infrastructure (which we believe should be abstract / raw resources) from the actual networks, configurations, applications, etc. General idea is that it allows you to be provider agnostic and ignore provider primitives, swap infrastructure as much as you want.

@Chris Ah sorry I think I meant regular pipeline variables and not Magic Variables -- my mistake. @Jake Thanks for mentioning this, think I'm going to go with this approach instead :)