In this post, I will share my study notes that I took while preparing for the exam Azure AZ400 “Implement an orchestration automation solution”.
Combine release targets depending on release deliverable (e.g., Infrastructure, code, assets, etc.)
There can be different kinds of deliverables. Some examples are:
- Infrastructure code — ARM Templates
- Web, desktop, mobile application packages
- Images or files
- Database migration scripts
There can be different release targets:
- Azure App Service
- Azure Functions
- Physical or virtual machine
- Azure Kubernetes Service
Correctly orchestrating these targets and deliverables means that everything works in the correct order.
Design the release pipeline to ensure reliable order of dependency deployments
When we try to release artifacts using the classic editors, we are introduced to a screen that looks more or less like this:
On the left, we can define a pipeline trigger.
The next step is to define which jobs are run for each stage. For example, for the Dev stage I have configured an ARM template deployment:
I configured the template section to pull the existing ARM template from my infrastructure repo.
It is possible to orchestrate the sequence of steps that produces a deployment and define which come depends on others.
In the trigger screen of a selected stage is possible to define that a stage would run after another.