Associate variables to environments
I'd like to be able to 'tag' an environment with one or more variables and then be able to use these variables in my release process.
My specific use case is that I'm deploying to Azure and want to set the slot based on the environment being deployed to (Production or Staging). This works nicely with the use of #{Octopus.Environment.Name} if my environments are specifically named "Production" and "Staging", but I'd like to be able scope my environments to project groups and this requires them to have unique names. So I name my environments something like "<project>-Production" and "<project>-Staging", unfortunately this breaks the ability to use the environment name variable for the azure slot.
