Why does Azure Staging function replace connection strings when I do Swap

Here are the details of the new Azure Staging Feature . And he says

Some settings from the phased version will be automatically copied to the production version - including such things as an override connection string, handler mappings, and other parameters that may have been configured. Other settings, such as DNS endpoints, SSL bindings, etc. will not change (make sure you don’t have to worry about SSL certificates used for an intermediate domain that overrides surfing production URLs, etc.).

What I don't understand, he says connection strings are overrides. When I change connection strings, they change each other. Therefore, in this case, my intermediate website database becomes a production database. I expect that it does not apply to connection strings at all, and my production site will continue to use the same database, but it uses an intermediate database because the connection string is changing each other.

Is it possible to set up an intermediate level website so as not to replace connection strings?

Has the design of the azure team changed a lot to use the test database on the production website?

+4
source share
1 answer

, . AppSettings - . , , , .

, , , . , , .

+3

Source: https://habr.com/ru/post/1526597/


All Articles