Book Image

Azure Resource Manager Templates Quick Start Guide

By : Ritesh Modi
Book Image

Azure Resource Manager Templates Quick Start Guide

By: Ritesh Modi

Overview of this book

Azure Resource Manager (ARM) templates are declarations of Azure resources in the JSON format to provision and maintain them using infrastructure as code. This book gives practical solutions and examples for provisioning and managing various Azure services using ARM templates. The book starts with an understanding of infrastructure as code, a refresher on JSON, and then moves on to explain the fundamental concepts of ARM templates. Important concepts like iteration, conditional evaluation, security, usage of expressions, and functions will be covered in detail. You will use linked and nested templates to create modular ARM templates. You will see how to create multiple instances of the same resources, how to nest and link templates, and how to establish dependencies between them. You will also learn about implementing design patterns, secure template design, the unit testing of ARM templates, and adopting best practices. By the end of this book, you will understand the entire life cycle of ARM templates and their testing, and be able to author them for complex deployments.
Table of Contents (12 chapters)
Free Chapter
1
Section 1: ARM Template Foundational Skills
6
Section 2: ARM Template Advanced Concepts

Nesting resources

We have already learned that resources can have parent resources, and that child resources can be provisioned only after a parent resource is already provisioned. In the next example, we will provision a parent resource (sites) using ARM template. You will notice that the sites resource has an internal resources element. This element can declare multiple child resources within it. A resource of connectionstrings type is created within this resources section. This particular resource acts like a child resource for the sites parent resource. If you think about it, a connectionstrings resource can only be contained within a web app (sites); it does not make sense to deploy a connectionstrings resource without a web app, because connectionstrings are eventually placed within the web.config file of a web app.

The complete code for the following template is available...