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.
Majid Ismail commented
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
(Test, Acceptation, Production), en in the bindings use a variable list, containing all the IIS bindings