This quickstart deploys a simple hello-world webapp to two regions in a staged manner using Azure Deployment Manager (ADM). For more information, see:
To complete the quickstart, you need:
-
An Azure subscription: if you don't have an Azure subscription, create a free account before you begin.
-
Install the Azure Az PowerShell: For the instructions, see Owerview of Azure PowerShell.
-
Install the Az.ManagedServiceIdentity module. Run the 'New-AzUserAssignedIdentity' cmdlet in a PowerShell window and if you get an error signature like "The term 'New-AzUserAssignedIdentity' is not recognized as the name of a cmdlet", run the following command in a PowerShell window opened in Administrator mode.
Install-Module -Name Az.ManagedServiceIdentity -
Install Git. For the instructions, see Install Git.
This project contains:
- The App directory: contains the code and scripts that make up the WebApp. This code at the time of this writing was taken from the Azure NodeJS based WebApp sample.
- The Deploy directory: contains the artifacts and scripts that are used to deploy the app using ADM. This also includes the templates/parameters files required to create the ADM resources that deploy the WebApp.
- The Deploy/ArtifactRoot directory: Contains the ARM Template and Parameters files for the WebApp deployment. These are given to ADM and used by ADM to orchestrate your WebApp deployment. The WebApp code in App directory is packaged into a zip as required for deployment and is stored in the bin directory.
- The Deploy/DeploymentManagerSetup.ps1 script: creates all the ADM resources, sets up a storage account, uploads the WebApp artifacts (from where this sample is run) to the storage account, creates a User Assigned Identity, creates a role assignment in your subscription for this Identity and proceeds to create a rollout.
-
Open Git Shell/Bash.
-
Run the following git command:
git clone https://github.com/Azure-Samples/adm-quickstart
-
Open Windows PowerShell.
-
Change directory to github\adm-quickstart\deploy.
-
Run the following command to connect to Azure:
Connect-AzAccount -
Launch the setup script by running the following command. You need to provide a subscription Id, resource group name (the script creates this resource group for you) and location for the resource groups. Make sure to give a subscription Id that is in the Azure account you logged in with. The resourceGroupName value is used to create a storage account and upload the artifacts required. Do not use uppercase letters or special characters in the resourceGroupName and limit the length to about 10 characters.
.\DeploymentManagerSetup.ps1 -subscriptionId "<subscriptionId>" -resourceGroupName "<resourceGroupName>" -location "<location>"
Once you run the script, you can open the resource group in the Azure portal and view the resources getting created. Make sure you select 'Show Hidden Types' option in the resource group view to see the ADM resources.
The WebApps are created in two different target resource groups named ServiceWUSrg and ServiceEUSrg. You can view the WebApp and dependent resources getting deployed to these resource groups once the script runs and as the rollout progresses. The rollout has a Wait Step after deploying to one region to demonstrate how you can introduce steps into your rollout to customize your deployment experience.
After the script completes successfully, it prints the command to track the rollout progress.
Run this command every 2-3 minutes to view the current status of the rollout and the resources that are being created. The rollout will reach a terminal state of 'Succeeded' when all the resources are deployed and all rollout steps are completed.
There are 2 resource groups created in addition to the one provided as input to the script and you can clean up all the resources created in your subscription by deleting these 3 resource groups. Search in the portal for the resource groups using and delete them.
Important: Deleting the resource groups will delete all the underlying resources created as part of this quick start.
Alternately, you can run the following commands from PowerShell to delete these resource groups.
Remove-AzResourceGroup -Name <resourceGroupName>
Remove-AzResourceGroup -Name <resourceGroupName>ServiceWUSrg
Remove-AzResourceGroup -Name <resourceGroupName>ServiceEUSrg
- ADM Overview: https://docs.microsoft.com/azure/azure-resource-manager/deployment-manager-overview
- Health Check integrated rollout with ADM: https://docs.microsoft.com/azure/azure-resource-manager/deployment-manager-health-check
- ADM tutorial: https://docs.microsoft.com/azure/azure-resource-manager/deployment-manager-tutorial
- ADM Health Check tutorial: https://docs.microsoft.com/azure/azure-resource-manager/deployment-manager-tutorial-health-check
If you'd like to contribute to this sample, see CONTRIBUTING.MD.
This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.