Keep IIS bindings not define in the 'Bindings' of the step

When deploying a website to IIS, all bindings are removed except those configured in the ‘Bindings’ section of the deployment step.

The site has so many bindings that I’d rather bind them in a different way (fex. custom step that uses comma seperated list of hostnames).

How can I keep these bindings?
I don’t believe it’s easy to plug in my own copy of Octopus.Features.IISWebSite_BeforePostDeploy
And I’d rather not create my own copy to be honest, because if OD’s version changes, mine won’t.

Hi David,

Thanks for reaching out. Octopus re-configures the existing site during the deployment, so unfortunately there is no way to keep the old bindings. What you could do is:

A) Manually add the bindings to the Octopus deployment step .

B) Have a pre-deployment step to export the bindings configuration to a file, and then a post-deployment step to import those settings into the site again.

Sorry its not better news.


Thanks Dalmiro for the options. I managed to work around it.
I do hope we’ll see a change in this in the future.