I suggest you...

← General

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.

41 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
AdminDalmiro Grañas (Support Engineer, Octopus Deploy) shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

5 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Daniel commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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.

General: Deployment features

Categories

Feedback and Knowledge Base

(thinking…)