Have a unified CLI command to manage deployments

[richardissimo]

Bicep deployments can be done with AZ CLI commands like this:

az deployment sub create
az deployment group create

Which command you use depends on where the deployment is being targeted, and the parameters of those commands vary. I'm not part of the private preview for deployments stacks, but from what I've seen, the command line for stacks looks to be following the same pattern.

Bicep has a way of referring to things like ResourceGroups and (Azure)Subscriptions, and it has a way of indicating things like "parent:" and "scope:", so my suggestion would be that those should be part of the Bicep file, rather than being part of the command line. Rather than

az stack sub create
az stack group create

It would be nice if we could just do

az stack create

And the Bicep file would declare what the scope was. This would allow the same command line to be used regardless of what was being deployed, and it would mean the definition of the deployment would be entirely contained in the Bicep file declaration (and parameters file), rather than the current situation, where part of the declaration is controlled by which command line was used to deploy it (sub or group), and the command line parameters (e.g. giving the resource group name that it's being deployed to).

[brwilkinson]

Please join the stacks preview to provide this info. It's in private preview right now, however it should be public preview very soon.

you can try to sign up here: https://aka.ms/getStacks

[brwilkinson]

Just to Add as well.

Currently you can deploy into a Management Group or a Subscription Scope and then target other scopes via Modules.

• Including other subscriptions or other resource groups.
• So you can essentially orchestrate via Modules and Modules can container conditions.