Today I am going to introduce you to the steps which you can use to swap deployment slots for production environment automatically in release pipeline by small manual intervention for approval/resume. Below are the steps which will help you to set-up slot automation.
Given any scenario this will work, but in my case it is like below.
I have release pipeline stetted up according to the environments.
Configuring slot swaps in Production
The Dev and QA environments orchestrate whatever flow you want in those environments (e.g. provision using ARM, deploy, run functional tests, run load tests etc.), and in this example don’t have any slot specific activity. Therefore let’s take a look at the production environment tasks itself directly:
(I’ve kept this to a minimum to keep it clearer, so no provisioning, running scripts or other activities.)
First deploy the web application to the staging slot in the production environment using the Azure App Service Deploy task:
Check the Deploy to slot option in the standard task, and then choose the Slot (I called the slot “staging” but you can use any name).
Next I’ve added an Agentless phase as it’s not going to delegate any actions to an agent, and added a Manual Intervention task. This causes the flow to pause until the manual intervention is completed by the specified approvers (groups and/or individuals). If it’s approved then it carries on, if it’s rejected (or times out and therefore is rejected) then the flow stops. In this case that works for me as I want the staging environment to be manually verified and then signed off as ok for final release to production. If it gets rejected then it never gets promoted from staging to production.
Finally, if the staging slot has been manually verified and is ready to be used, then we can initiate the actual slot swap (in an agent phase) using the Azure App Service Manage task:
The staging and production slots will then be swapped over, leaving the old production version in the staging app and the latest version in the production slot.
This flow supports the actual slot swaps being automated, but with manual approval. A nice side effect of the slot swap is that should there be a problem, the slot swap can be reversed to redeploy (rollback) the old version of the app now in the staging slot.
Happy Learning/Innovating Azure.