Bicep support and dev container

[mcollier]

Purpose

• This PR adds initial support for Azure Bicep to the ACI and AKS deployment options. This PR also adds a Visual Studio Code dev container.

Does this introduce a breaking change?

[ ] Yes
[X] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[X] Feature
[X] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[X] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

• Open the project using Visual Studio Code and the provided dev container.

• Follow the instructions in the Azure-Container-Instances or Azure-Kubernetes-Svc folder to provision the necessary resources using Azure Bicep.

• Test the code

What to Check

Verify that the following are valid

• The dev container starts without error and necessary tooling/extensions are installed.
• Appropriate Azure resources are provisioned.

Other Information

• This PR does not modify the ARM templates, nor modify how the Deploy to Azure button functions.

[mcollier]

@tawalke I pushed an update which replaces the previous ARM templates with an ARM template generated from the Bicep files (using the az bicep build --file main.bicep --outfile azuredeploy.json command). The README files were updated to link to the new azuredeploy.json files.

[tawalke]

@tawalke I pushed an update which replaces the previous ARM templates with an ARM template generated from the Bicep files (using the az bicep build --file main.bicep --outfile azuredeploy.json command). The README files were updated to link to the new azuredeploy.json files.

I would like this to additional option vs. in lieu of so folks have both. Can you update do this is an additional offering of bicep. Thanks!

[tawalke]

This repo is going to be changed to public today.

[mcollier]

@tawalke I’m not understanding. Can you please expand on the request?

The PR contains both an ARM and Bicep template.

[tawalke]

@mcollier reviewing.