Azure Swap Deployment Slot Sticky Settings Not Working

1
votes

I have configured a production and staging slot in Azure, with each slot using it's own SQL Azure database.

The connection string for each is configured to be "sticky".

enter image description here

However when I go to swap the production slot (destination) with the staging slot (source) I get the following warnings.

enter image description here

The informative message is telling me that the the connection string from staging will overwrite the production one. Additionally the earlier warning is telling me that the DefaultConnection settings does not exist in production - BUT it does and it is also sticky.

Finally the fist two warnings are complaining about connection strings missing from both staging and production - these were indeed deleted from both as no longer required. But what are they listed as missing - what is the source of truth?

Am I missing something?

This MSDN question might be useful to follow

1
azuredeployment

1 Answers

1
votes

Whilst I still don't know why the warnings are occurring, they would appear to be nonsense - if I go ahead and swap the slots I get what I expect - everything but the connection strings swap. Production still points to the production database and staging still points to the staging database.