Create Environment with Azure Deployment Slots
And automate with Azure CLI script on Mac
When deploying your application using a serverless solution, for example, Azure Functions or Azure App Service, you can use deployment slots to set up environments, such as a staging environment.
The deployment slots can be used for A/B testing and canary deployment, controlling the exposition of a specific version to a particular public or a slice of your requests. Then, promoting the tested version into your main slot is easy as clicking the swap button.
The Scenario
Recently I had to replicate my test environment, used for user acceptance test, to make it available to an external vendor, as a development environment.
The application is currently a colossal monolith application that, in the last couple of years, has been decoupled in separate components — or modules.
The monolith runs on a Virtual Machine hosted on an IIS, and it was decided just to duplicate the VM and configure it to be the development environment.
But the modularized components are already developed and planned to run in the cloud as AppService. For those components, it was decided to create the deployment slot.
