| page_type | languages | products | description | urlFragment | ||
|---|---|---|---|---|---|---|
Learning Azure Resource Manager (ARM) template |
|
|
A series of tutorial paired with videos to guide you through learning the best practice about Azure Resource Manager (ARM) template. |
update-this-to-unique-url-stub |
In this repository you will find a series of tutorial paired with videos to guide you through learning the best practice about Azure Resource manager (ARM) template.
Each video is featured in the same page as the content. The videos are part of Azure DevOps - DevOps Lab show.
In this tutorial you will learn the what, the why about Azure Resource Manager (ARM) template. Why why talk about declarative, idempotency.
Now it's time to code. This session will introduce Visual Studio Code tools, and show you how to create your first template from snippet, and how to deploy it.
This is where we will define our parameters. There is multiple type of parameters but before we go list them and see some scenarios, let's understand how parameters are defined.
What are template functions, show common functions, add and use a template function.
Variables are very useful in all king of scenarios to simplify things. Azure Resource Manager (ARM) templates aren't an exception and the variable will offer great flexibility. In this chapter, we will explain how you can use variables inside your template to make them easier to read, or to use.
What are outputs and how are they used.
Using dependencies to control resource deployment order.
How to modularize templates using nested and linked templates.
How to do loops and why would you do it.
The ARM template is very powerful and useful, we can agree on that. However, something it could be hard to get started. In this tutorial you will learn tips and tricks to start from scratch with existing template or export the template from existing resources.
Deploy a complete ARM template using GitHub Actions
Deploy a complete ARM template from Azure DevOps
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
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.