Skip to content

Latest commit

 

History

History
40 lines (30 loc) · 2.53 KB

bicep.md

File metadata and controls

40 lines (30 loc) · 2.53 KB
Raw

Bicep Azure Bicep Logo

About

Bicep is a DSL created and maintained by Microsoft starting with v 0.3 onward. Bicep templates will compile into Azure Resource Manager (ARM) templates and are deployed similarly. In fact there is even a decompile which take a best guess conversion into a Bicep file. If you want can also run a bicep build command which will compile the Bicep file into an ARM template for evaluation.

Some Pointers

  • There is no state file
  • Anything achievable in ARM can be done in Bicep
  • Bicep is released monthly
  • Day 0 support for any Azure resources, even those in private preview
  • Azure is only provider available
  • Easily declare individual Azure Resource provider API versions

How It Works

The Azure CLI will compile a Bicep file into an ARM Template. This template will be sent directly to the Azure Resource Manager.

Diagram illustrating Azure Consistent Management Layer

Source From: Microsoft Docs

PreReqs

Validating Changes

The best way to validate changes would be to leverage the Azure CLI what-if command similar to: az deployment sub what-if --location EastUS --name azureADOCLIDeployment --template-file main.bicep --parameters parameters/dev.eus.parameters.json

For more information check ouf the ARM Template deployment what-if operation

Deploying

Deployment for these examples are done at the Subscription level. This is done to ensure full deployment by creating the required Resource Group.

az deployment sub create --name storageDeployment --location eastus --template-file main.bicep --parameters parameters/dev.eus.parameters.json

Links