"deploy" command for bicep CLI

[alex-frankel]

This would both compile the bicep code into ARM JSON and deploy it. I'm not sure if it would need to generate a temporary azureDeploy.json file or if it could keep everything in memory.

As a prerequisite, you would need to have either Az CLI or Azure PowerShell installed and the Bicep CLI would simply call that. I'm imagining users can create a config file to specify all the parameters required for a deployment:

• Az CLI or PowerShell
• Name of parameters file (we will assume a default of parameters.arm or something like that, btw we need to figure out parameters :) )
• target scope
• use --confirm or not

[alex-frankel]

@artursouza - can you point us to the CLI extension that you wrote to do this?

[alex-frankel]

cc @rynowak who may also know

[rynowak]

https://github.com/Azure/azure-bicep-cli-extension/

[alex-frankel]

This should be fixed by allowing .bicep files to be deployment via az deployment group create -f main.bicep (and equivalents)

[artursouza]

@alex-frankel I agree, this feature belongs to az cli (or az cli extension), which will eventually lead to issue #91

[alex-frankel]

Closing since #858 is done