In this module you will create an Azure release pipeline that will deploy the configurations to a 'test' environment, wait for human approval and then deploy the configuration to a 'production' environment.
Create a new release pipeline. YAML based release pipelines are in preview and do not yet support manual approvals. You will work with classic pipelines for this workshop.
Pipelines > Release > New Pipeline
Start with an empty job pipeline template.
Name the stage Test.
Add the deployment artifacts with the Add button.
Select the build pipeline and click Add.
Select the stage to edit the stage tasks.
Select Agent job and update the Agent pool to use Hosted Ubuntu 1604.
Add a Command Line task, give it a name of Deploy Hello World.
Copy in the following commands.
RELEASE=Hello-World-$(Release.EnvironmentName)
cd $(Release.PrimaryArtifactSourceAlias)/drop/modules/hello-world
terraform init
terraform plan --out plan.out -var resource_group=$RELEASE -var dns-prefix=$RELEASE
terraform apply plan.out
Finally, add Azure credentials to the deployment task.
Select Variables > Variable groups > Link Variable Group > azure-credentials > Link.
Click back on Tasks. On the Terraform Deploy Test, expand Environment Variables and add the following variables and values. Encrypt each with the lock
| Name | Value |
|---|---|
| ARM_CLIENT_ID | $(ARM_CLIENT_ID) |
| ARM_CLIENT_SECRET | $(ARM_CLIENT_SECRET) |
| ARM_TENANT_ID | $(ARM_TENANT_ID) |
| ARM_SUBSCRIPTION_ID | $(ARM_SUBSCRIPTION_ID) |
When done, the task should look like this.
Click Save > ok.
Click the Create release button > Create > Select the release.
And click the In progress link to see the deployment progress.
If everything went according to plan, you should have a successful release.
Return to the release pipeline, click Edit, and clone the test stage.
Name the new stage Production and click save.
Return to the pipeline and select pre-deployment conditions on the production stage.
Select Pre-deployment approvals, and add your account as an approver.
Click Save and Ok.
Click Create Release and Create to start a new release and select the release link to observe the status.
Once the test release has successfully deployed, the production release will need to be approved. Check out the test release, and if it looks good, approve the production release using the approve button.
When done, you should see both the test and production release in the Azure portal.
These Azure Pipeline examples have not included remote state. As an additional challenge, see if you can insert the logic to store both the test and production state in an Azure backend.