Allow prompt variables to be scoped to more than just environments
As of 3.0.11. prompt variables can only be scoped to environments. It would be good to be able to scope them to steps, roles and machines as well.
Christopher Duffield commented
This functionality is needed as when something deploys to production across two servers that need two separate variables it just deploys the same variables across all Production servers unless we actually have every production server as its own environment and then add process steps for each server. It is not an effective way to conduct releases.
Prompted variables with default values scoped to channels (or even channels where the same variable wasn't prompted) would be extremely useful.
Tim Wesemann commented
same here, only tenants. was trying to make a "lab" tenant where we could let people pick a URL to deploy personal builds to, guess i'll have to settle for basing it on username. had the potential to be pretty powerful if it weren't for this (seemingly arbitrary) limitation.
Colin Pear commented
This should be modified to read allow template variables to be scoped to more than environments. And this should be more than just Project Templates. We should have the ability to scope Library Set Variable Templates as well.
B Au commented
I agree. We need Channel scoping.
Benjamin Rice commented
And I definitely believe that channel scope should be included, if not take precidence.