[Request] print the URL to the resource groups deployment page

[paulyuk]

When you're deploying AZD and bicep, the most useful diagnostics blade IMO is the deployments for the resource group (not the blade for this deployment). The reason why is it shows every bicep module in your AZD provision as a deployment, and for each you see status (pass/fail/error), plus the inputs, outputs, and templates that are invaluable for diagnostics. This should be shown both when a deployment succeeds and fails.

@jongio @ellismg @savannahostrowski

[ellismg]

We support two forms of deployment today via ARM:

1. Subscription level deployments - This is what most of our templates use today, and what we started with. In this world, the root deployment is created at a subscription level and that deployment creates a resource group and then the sub deployments that Paul shows here in order to provision all the resources (each one of these deployments shown corresponds to a module, because each module ends up as a separate deployment).
2. Resource group level deployments - This is new in 1.1.0, guarded by an alpha flag, and works similar to above except the root deployment is created inside a resource group (it would be another entry in the list Paul has in his screen shot).

In both cases, these nested deployments should be visible from the root deployment, so you can navigate to the sub deployments from the link we print to the console, but there is an extra step.

If we decide we are going to do this - I suspect we'll need to figure out what we want to do for subscription level deployments that end up allocating multiple resource groups. Do we print a link to the deployments tab for each resource group?

[paulyuk]

Hi, I feel the multi RG is less common, and yes in that case printing one URL for each RG is ideal (or even the first one could be ok).