10 Template Specs and Bicep Registry: Building a repository of templates
This chapter covers
- Storing ARM and Bicep templates as a reusable Azure resource
- Deploying Template Specs using the CLI, PowerShell or the portal
- Referencing Template Specs from another template
- Alternatives to using Template Specs
Imagine working at a large company with many teams, and all of them are running applications on Azure infrastructure. Most of these applications run on similar infrastructures, like virtual machines, Kubernetes, or App Service Plans. No one wants to write the same ARM or Bicep templates over and over to create those infrastructures, right? And besides the repetitive work, most companies have some standard approach to these infrastructures that they want to impose on every team.
In this chapter, you learn how to store ARM or Bicep templates in Azure and make them available for others to re-use your templates.
10.1 Use case: a repository of compliant resources
Let’s say you work at Doush Bank, a bank serving millions of customers all over Europe. A bank like this has hundreds of applications maintained by hundreds of development and operations teams.