Azure / Azure/bicep

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

Open
#3,915 3 comments 2 reactions 0 assignees View on GitHub
enhancement story: visualizer
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

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](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-history?tabs=azure-portal), 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:
![image](https://user-images.githubusercontent.com/38542602/128421495-c23a8e9a-7a93-4e21-a8c9-365d225fa5a8.png)

GitHub Actions:
![image](https://user-images.githubusercontent.com/38542602/128438348-07979749-c18f-49df-85d4-798f89169626.png)

DevOps release pipelines:
![image](https://user-images.githubusercontent.com/38542602/128438405-aa56c2b8-d1cc-4362-9479-b19b33a74574.png)

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating the Bicep visualizer and its Azure deployment integration, then define how ongoing, completed, and failed operations should appear alongside the Bicep file, including the proposed resource errors and navigation interactions.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.