Allow Bicep visualizer to visualize diagnostics from a running or completed deployment

[anthony-c-martin]

It would be really nice to be able to log in to an Azure environment, and have the visualizer report on on-going deployment operations or completed/failed operations in real-time alongside the Bicep file which triggered the deployment.

Much like the Azure Portal experience, but with more interactivity (seeing errors on resources visually, being able to jump to resource/module definitions, or being able to highlight lines of code with errors once we have #855)

Some (old school) prior art from the SQL query analyzer - where you can inspect nodes to find out more information about each operation:

GitHub Actions:

DevOps release pipelines:

[alex-frankel]

This would be very cool!

Curious how we would handle loop'd resources. I think this only shows as one resource in the visualizer, but would show up as N resources in deployment operations.

Putting it in "Not as fast" only because I think we will have trouble prioritizing it, but I also don't have a good understanding of cost.

[afscrome]

What if the deployment commands included a link to the existing portal deployment experience?

Starting Deployment.
Deployment name is EXAMPLE. View progress at https://portal.azure.com/#blade/HubsExtension/DeploymentDetailsBlade/overview/id/{DEPLOYMENT_ID}
Successfully deployed the template.

Obviously a native UI would be much nicer, but I'd assume a hyperlink could be added much more easily as a short term solution. It would also be highly beneficial for CI scenarios where you couldn't render a UI to show progress.

[alex-frankel]

What if the deployment commands included a link to the existing portal deployment experience?

@shenglol / @stephaniezyen might be secretly working on a UX redesign of the CLI deployment progress/output that might include this ask ;)