App Service Public SSL Certificates persist When Swapping Slot
Currently, if a Web App slot (ex: "staging") is created from an existing Web App that has Public SSL Certificates configured, these are not present on the new slot.
In addition during a slot swap, the "production" slot does not persist the Public SSL Certificates. The configuration for the Public SSL Certificate moves to the "staging" slot.
This behavior does not appear for other configurations such as Private SSL Certificates or AppSettings and could lead to "production" issues if the Public SSL Certificate is expected on the Web App.
The consumer recourse currently is to re-apply the Public SSL Certificates each time a slot is created and swapped which seems unnecessarily redundant.
It would be a greatly appreciated feature if either the Public SSL Certificates persisted on "production" similar to Private SSL Certificates or if the creation of a new slot could include the configuration of the Public SSL Certificate.
I've just warmed to the idea of deployment slots then I discover this issue! :-(