Tutorial : Developing ARM Templates using Azure Bicep

 In this article, we will learn how to use Azure Bicep for developing ARM templates. The Azure Bicep is an abstraction on top of the ARM JSON syntax that makes the authoring experience of ARM templates easier.

Azure Resource Manager templates (ARM templates) are used to implement infrastructure as code for your Azure solutions. These templates are a JavaScript Object Notation (JSON) file that is used to define the infrastructure and configuration for the project. It uses declarative syntax, for stating your intentions to deploy without having to write the sequence of programming commands to create it.  In the template, you just specify the resources to deploy and the properties for those resources.

Implementation:

Follow the below steps to develop ARM templates using Azure Bicep:

Step 1: There is a VS Code extension for Bicep. Let’s install it.  


Step 2: To make it work completely, we’ll open a terminal. We already have the Azure CLI installed so, we can now do az bicep install. 

Step 3: We’ll create a file called main. bicep. Visual Studio Code will recognize it and give us some tools to work with. For instance, when we start typing, it suggests code snippets for us, like this one for an Azure App Service plan.



Step 4: We’ll continue here with web and this one for an App Service Web App. 



Step 5:The snippets have default names in them, so let’s change this one for the App Service Plan. This doesn’t have to be unique, and we will use it in here so that the web app uses this App Service Plan. 



Step 6: We don’t need tags for the web app, so we’ll delete those. Let’s see some Bicep. We can create a parameter for the name, so a string parameter, and use that here. This is useful for a user to fill in as a web app needs to have a unique name.



Step 7: Bicep has lots of goodies like annotations. This parameter has a minimum length of 1 and a maximum length of 59. We have full IntelliSense. Finally, we’ll make the web app depend on the App Service Plan. This ensures that the App Service Plan gets deployed first and the web app only deploys when the App Service Plan succeeds.



Step 8: With the button on the right, we can open the visualization of the Bicep file. This is very useful when we have resources that depend on each other. The Bicep file can become very complex.



Step 9:  Let’s deploy this. We’ll open a terminal and now we’ll do az deployment group create. This will deploy to a resource group that already exists. We need to fill in a name for the parameter. 

The web app and App Service Plan were deployed successfully.



Azure Bicep is an infrastructure as code language that makes it easy to create ARM templates using IntelliSense, code snippets, and compiler error checking. Go and check it out.

Comments

Post a Comment

Popular posts from this blog

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Agile Retrospective

Image
  Guide to agile retrospectives for continuous improvement An agile retrospectives is an opportunity for agile development teams to reflect on past work together and identify ways to improve. Agile teams hold retrospective meetings after a time-boxed period of work is complete (typically a sprint lasting two to four weeks). During the agile retrospective, the team discusses what went well, what did not go as planned, and how to make the next work period better. Even if you are not on a development team, you can probably relate to the concept of retrospection. Have you ever worked hard on something only to realize later that you should have done it differently? It is not always a good feeling, but the solutions you uncover in hindsight can be valuable input for your next try. The same goes for your successes — acknowledging what went well and is worth repeating can be just as impactful. What is an agile retrospective? In short, an agile retrospective is a meeting...
Read more

Agile product management

Image
  What is agile product management? How do we define agile product management? It is a product development philosophy that emphasizes a flexible and human — rather than a rigid process- or tool-oriented — approach to defining product strategy and carrying out work. Teammates focus heavily on customer feedback to make improvements and adjust roadmaps throughout the product management process. This creates more responsive teams, leads to quicker iterations, and creates a more lovable experience overall. Benefits of agile product management Agile redefines how product managers think about planning and building products. Traditionally, new customer experiences were planned, designed, implemented, and tested in a step-by-step way. This meant that new functionality was delivered sequentially. Once requirements were defined and handed off to the development team, it was difficult to make any changes. The failure rate of large-scale and lengthy software development proj...
Read more