I suggest you...

Make variable list usable for configuring IIS bindings.

When adding a binding to IIS in Octopus, you can only use seperate variable. Every binding needs a new variable. Some of our deployments have over 50 bindings. We create each binding separate. If we use a variable list only the last item of the list end up in de IIS binding. It would help us a lot if we could ad three generic bindings (Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings.

51 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Wilfried Jonker shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

2 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Majid Ismail commented  ·   ·  Flag as inappropriate

    I really like to have this feature, as its annoying when you have n number of customer and have different binding requirements. We have to add binding and then create a new release, which is annoying.

  • Brandi Fehn commented  ·   ·  Flag as inappropriate

    (Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings

Feedback and Knowledge Base