Deployment slots, when swapped slot will merge back from prod slot?

Question

Deployment slots, when swapped slot will merge back from prod slot?

Bhargav Pasarla 120

Consider, staging slot is trying to swap with prod slot.

staging have changes and prod needs to have the new changes. when we try to deployment slot swap from staging to prod, Prod will have the new changes from staging and staging will have the old prod version.

Now I need staging also to have the new changes, like the exact replica of prod new version. How it is can be done?

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-01-02T18:59:13.9666667+00:00

@Bhargav Pasarla , Just checking in to see if you had got a chance to see the previous response. If the answer helped (pointed, you in the right direction) > please click Accept Answer Or please share the requested/more info to help you better.

Accepted answer

1 additional answer

Your answer

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-01-02T18:59:13.9666667+00:00

@Bhargav Pasarla , Just checking in to see if you had got a chance to see the previous response. If the answer helped (pointed, you in the right direction) > please click Accept Answer Or please share the requested/more info to help you better.

Answer 1

@Bhargav Pasarla , As Paul suggested, by having separate deployment slots for production, staging, and development, you may test your changes in a non-production environment before deploying them to production.

Based on my understanding your scenario, if your requirement fits, you may also checkout the following approach:

You may leverage/perform a swap with preview. This will allow you to validate that the app runs with the swapped settings before completing the swap. During the swap with preview, the source slot is also warmed up before the swap completion, which is desirable for mission-critical applications. If you cancel the swap, the configuration elements will be reapplied to the source slot.

To swap with preview, you can follow the steps in Swap deployment slots but select Perform swap with preview. The dialog box shows you how the configuration in the source slot changes in phase 1, and how the source and target slot change in phase 2. When you're ready to start the swap, select Start Swap.

After the swap, the staging slot will have the new changes from the production slot, and the production slot will have the old version from the staging slot. If the changes swapped into the production slot aren't as you expect, you can perform the same swap immediately to get your "last known good site" back.

Checkout : What happens during a swap || Swap operation steps

Additionally, Auto swap streamlines the deployment process by automatically swapping the app into production after it's warmed up in the source slot. When auto swap is enabled from a slot into production, every time you push your code changes to that slot, App Service automatically swaps the app into production after it's warmed up in the source slot.

After you configure auto swap, every time you push your code changes to the source slot, App Service automatically swaps the app into the target slot after it's warmed up in the source slot.

Note that auto swap isn't supported in web apps on Linux and Web App for Containers. Also, make sure to test auto swap on a non-production target slot before configuring it for the production slot.

Please let us know if you have any further questions or if I have misunderstood your ask or provide more info about your exact requirement.

Bhargav Pasarla 120 Reputation points

2024-01-04T17:22:39.3033333+00:00

My point here is if staging is replaced with older version of Prod, if there is a dependent app on staging then that dependent app will be impacted with this swapping right? even if we have dev slot, till the time we move something from dev to stage, the dependent apps are impacted. and this is something we are causing it with the swapping and not any unpredicted issue.

Why do someone need to spoil the staging slot and then try to recover it?

That's where I don't understand the concept of swap and Please provide more insights if I understand it wrongly.
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2024-01-08T18:30:02.3166667+00:00

Thanks for the follow-up.

You are correct that if a dependent app is running on the staging slot and the staging slot is swapped with an older version of the production slot, the dependent app will be impacted by the swap. This is because the swap replaces the entire contents of the production slot with the contents of the staging slot, including any dependent apps that may be running on the staging slot.

However, it is important to note that the purpose of the staging slot is to allow you to test and validate changes to your application before deploying them to production. By swapping the staging slot with the production slot, you can ensure that the changes have been thoroughly tested and validated before they are deployed to production.

If you have a dependent app running on the staging slot, you may want to consider deploying it to a separate slot or environment to avoid any impact from the swap. This can help ensure that the dependent app remains available and functional during the testing and validation process.

So, the staging slot can be used to test and validate changes to your application without impacting the production environment. If the changes are successful, you can then swap the staging slot with the production slot to deploy the changes to production. If the changes are not successful, you can simply discard the staging slot and start over with a new staging slot.

Answer 2

Paul Stoner 6

I do this by having the following deployment slots: production, staging, and development. I then make sure the development slot has the exact same code base as staging (before the swap to production), and then I simply swap the development slot with staging.

I'm not certain there is another way to accomplish this

Bhargav Pasarla 120 Reputation points

2024-01-05T16:24:20.81+00:00

Thanks @Paul Stoner This is a good workaround.

Share via

Deployment slots, when swapped slot will merge back from prod slot?

1 additional answer

Your answer