od-temp.example.com binding in new IIS Website with merge existing

[tw17]

Prerequisites

• I have verified the problem exists in the latest version
• I have searched open and closed issues to make sure it isn't already reported
• I have written a descriptive issue title
• I have linked the original source of this report
• I have tagged the issue appropriately (area/*, kind/bug, tag/regression?)

The bug

When we do an IIS deployment with the new "Merge with existing bindings" option, our temporary binding od-temp.example.com gets left behind if the site is created for the first time

What I expected to happen

The temp binding od-temp.example.com should be removed

Steps to reproduce

1. Create a project with a deploy to IIS step
2. Make sure the "Merge with existing bindings" option is selected
3. Deploy and observe the bindings on the IIS site.

Affected versions

Tested in
Octopus Server: 2019.13.0

[tw17]

Unwanted od-temp.example.com binding in new IIS Website with merge existing bindings

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.