Add an option to only create a binding in IIS if it does not already exist
We would really like to have an option to leave bindings alone in IIS if they already exist.
I configure a single binding as a templated deployment step. I would like octopus to automatically create the IIS app and bindings in the event the app pool and website doesn't exist - but if it does already exist I'd prefer it not to reconfigure the bindings.
This is useful when we create website aliases for production environments which don't fit the normal QA and UAT environment setup (but they happen to use the same steps).
Best would be a checkbox:
"Overwrite any existing bindings" - defaulted to true for backwards compatibility.
This will ship in `2019.5.11` and in the next LTS
Samantha Bowers commented
Do you have more examples on how to accomplish this? I can't seem to find any examples on how to 'Skip" adding the bindings if they currently exists.
Same here, I have to find a way to backup and then restore a large number of bindings for a few sites. It would be way easier if I could just tell Octopus to leave them alone.
The actual problem is that I'm adding new bindings quite often (both http and https) and using variables is not exactly an option. I'll still have to do quite a lot of micro-managing in Octopus.
What would be really useful for us:
create a binding for a new site, with a specific certificate.
We have other sites using the same port (443) but with different certificates.
When using Octopus, the bindings are updated for all sites! so a site that is not deployed using octo ends up with the certificate specified in our deployement process.
We lost hours to understand why another site did not work anymore.
Mohammad Imran commented
This functionality is very much required. I'm facing this issue also, I have website which is having about 30 bindings and I dont want to put all binding in Octopus. If we can have an option to not reconfigure the IIS binding in case atleast whatever binding present in Octopus matches with IIS on server or an option to select not to reconfigure the IIS binding.
This is a great idea.
Martín Ferrari commented
This would be useful in our scenario too. Some bindings are created outside of deployment, we should not delete them.
Shaun Little commented
For anyone who's still waiting for this to get resolved (specially if you ran into this while trying make Octopus work with LetsEncrypt) ,I ended up using "Deploy a Package" template rather than using "Deploy an IIS Website" - to copy the files to the IIS Application folder.
Is there any solution planned for this?. I'm also facing issues with iis bindings during deployment. My scenario is a multi-tenant web application in which bindings are created dynamically when the customer creates itself a new account and a private environment is set for him. For this reason it is not suitable to set fixed bindings during deployment to production.