Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output the dependency graph of produced template #2290

Closed
stan-sz opened this issue Apr 16, 2021 · 3 comments · Fixed by #2357
Closed

Output the dependency graph of produced template #2290

stan-sz opened this issue Apr 16, 2021 · 3 comments · Fixed by #2357
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@stan-sz
Copy link
Contributor

stan-sz commented Apr 16, 2021

Bicep could produce a textual/visual (graphviz?) dependency graph of the template. I envision such graphical representation can be helpful for human-checking more and more complicated templates, especially with the new parent/child syntax and the possible dependencies between various children of various parents.

Describe the solution you'd like
A few options:

  • bicep visualize command to consume JSON/bicep template and produce the visual type (similar to the what-if)
  • --verbose param of the build command to do the above as a last step of the transpilation
  • kudos for getting a graph widget in the VSCode plugin for an open bicep file
  • close this item as won't fix and defer this work to other (external) tools
@stan-sz stan-sz added the enhancement New feature or request label Apr 16, 2021
@ghost ghost added the Needs: Triage 🔍 label Apr 16, 2021
@MarcusFelling
Copy link
Collaborator

Are you looking for something like Azure portal ARM Visualizer, but in VS Code while authoring? Similar to the ARM Template Viewer extension?

@stan-sz
Copy link
Contributor Author

stan-sz commented Apr 20, 2021

Yes. Also a textual output (similar to what terraform plan) could be sufficient.

@stan-sz
Copy link
Contributor Author

stan-sz commented Apr 23, 2021

@shenglol your item #2358 looks like it's addressing the problem raised here :)

@shenglol shenglol self-assigned this Apr 26, 2021
@shenglol shenglol added this to the v0.4 milestone Apr 26, 2021
@ghost ghost locked as resolved and limited conversation to collaborators May 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants