11 Using Deployment Stacks for grouping resources

 

This chapter covers

  • Why you need another mechanism for grouping resources by their lifetime in Azure
  • What Deployment Stacks are and how you can use them for grouping resources
  • How Deployment Stacks replace Blueprints, somewhere in the future

In the chapters so far, you have learned all about creating and updating Azure resources through IaC. In a template, you describe how you want your resources to be configured, and the Azure Resource Manager makes it so by creating or updating resources. Up to now, no attention has been given to removing resources you do not need anymore, except for mentioning the complete deployment mode in chapter 4.

In that chapter, you learned that complete deployments were a powerful but risky method for removing resources you do not need anymore. In practice, the risky side of complete deployments is why complete deployments are not frequently used in the real world. Some teams use them in non-production environments, but complete deployments into production environments are rare. You will revisit this in more detail later in this chapter.

11.1 Grouping resources by their lifetime

 
 

11.1.1 Deployment mode complete is not good enough

 
 

11.1.2 Deployment Stacks to the rescue!

 
 

11.1.3 Creating a Deployment Stack

 

11.1.4 Updating a Deployment Stack

 
 

11.1.5 Removing a deployment Stack

 
 

11.2 Provisioning resources for others, but disallowing updates

 
 

11.2.1 Azure Blueprints: a first solution

 
 
 

11.3 The future of Deployment Stacks

 
 

11.4 Summary

 
 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage
test yourself with a liveTest