3

I'm trying to understand how deployment slot works (https://learn.microsoft.com/en-us/cli/azure/webapp/deployment?view=azure-cli-latest).

I ran the following command in order to create a new staging slot:

az functionapp deployment slot create --name MyFunctionapp --resource-group MyResourceGroup --slot staging

And I see two deployment slots in 'Running' state. Is it supposed to run only 1 slot at a time? If so, how do I stop one?

enter image description here

I have a few app settings in Configuration. What does this checkbox indicate? Please help me understand.

enter image description here

user989988
  • 3,006
  • 7
  • 44
  • 91

2 Answers2

6

Is it supposed to run only 1 slot at a time?

No, they are both supposed be running. When you create a staging slot, you now have 2 instances of your app running. One is your staging slot (where you can first test your application before swapping it with production), and the other is the production slot. see : https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots#add-a-slot

I have a few app settings in Configuration. What does this checkbox indicate? The checkbox indicates whether or not the app config value is a slot setting. if the app config value is a slot setting, then it is not updated when a swap happens between say staging and production. But if it is not a slot setting, and you swap production with staging, then the app config value in your staging environment with override the value in the production app config. In other words, selecting this check box tells App Service that the setting is not swappable. see : https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots#which-settings-are-swapped

Rimaz Mohommed
  • 1,176
  • 10
  • 16
  • Let's say I have 2 azure functions: Fun A & Fun B. Fun A has 2 slots - production, staging and Fun B has 2 slots - production, staging. Fun B is a service bus trigger function - when a messaged is passed to a queue from Fun A, Fun B gets triggered. Means, Fun B has a dependency on Fun A. Let's say I made some changes to Fun B and these changes are deployed to staging slot of Fun B (not production slot). A messaged is passed to the queue from Fun A, Fun B gets triggered. What happens now, does the code in both staging slot/production slot run? Please help me understand. – user989988 Apr 15 '22 at 21:31
0

Deployment Slot Settings checked means this setting is sticked to the slot.
So when you swap from staging to production and this flag is checked on staging this configuration will not be used on production.

You can set standard configurations like this. (No flag in UI)

az functionapp config appsetings set -g EVGroupused" -n "evgadmin" -s staging --settings CosmosDbConnectionString=$cosmosdbConnectionString

The same configuration but with flag checked.

az functionapp config appsetings set -g EVGroupused" -n "evgadmin" -s staging --slot-settings CosmosDbConnectionString=$cosmosdbConnectionString

So: --settings versus --slot-settings It took me a while to figure this out.

njefsky
  • 327
  • 2
  • 5