Skip to content

Latest commit

 

History

History
40 lines (26 loc) · 2.13 KB

Bicep-Challenge-01.md

File metadata and controls

40 lines (26 loc) · 2.13 KB
Raw

Challenge 1 - Basic Bicep

< Previous Challenge - Home - Next Challenge>

Pre-requisites

Make sure your machine is set up with the proper tooling: IaC Bicep Hack - Prerequisites

Introduction

The goals for this challenge include understanding:

  • Why Bicep is an improvement over the current ARM template language
  • How Bicep works
  • How to write ARM templates in Bicep

ARM templates are very powerful and provide a lot of functionality. However, many customers have commented that they are hard to learn and can be difficult to work with, especially because they are written in JSON with additional functionality embedded through template functions.

Bicep is a new language for ARM templates. Unlike JSON, it's not a general-purpose file format - it's designed specifically for deploying resources into Azure. Its goal is to be a much cleaner, more readable language.

Bicep templates are transpiled into standard JSON ARM templates in a similar way to how TypeScript is transpiled into JavaScript. This conversion is currently achieved using the Bicep CLI, although in future the transpilation step may be embedded into the Azure CLI and other tooling as well.

Your first challenge is to create a simple Bicep file that takes an input storage account name to create an Azure Storage Account, and returns an output storage account id. The goals here are to understand:

  • Core elements of Bicep file and different ways to deploy it.
  • How & where to see & troubleshoot deployments in the portal.

Description

Develop a simple Bicep file that takes inputs to create an Azure Storage Account, and returns an outputs.

  • Create a simple Bicep file
  • The file must take inputs: location and a unique storage account name
  • The output must return a storage account id
  • Deploy it using the Azure CLI
  • Deploy it using the Azure PowerShell Cmdlets
  • Observe the deployment in the Azure Portal

Success Criteria

  1. You can deploy Bicep file using both the CLI and PowerShell
  2. You can view the deployment in the Azure Portal and view the inputs & outputs