You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A little something the community might find useful.
This is a python script that will pull remote state of terraform resources (this is known to work with Azure and Terraform 1.3.0) from a storage blob in Azure. It will use that to generically map those resources to diagram node types. It's rudimentary at this point and only covers a few node types in the resource mappings. But, it will automagically create a dependency diagram from remote state.
If your resources have tags or other metadata that indicate any information for data or workflows that would be good to diagram, you could alter the script to look to include those in the edges as well/in place of a simple dependency graph which is what this currently generates.
Assuming you have remote state stored in an Azure storage blob, just fill in the related fields at the bottom with your details, update the resource type mappings as needed and give it a run.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
A little something the community might find useful.
This is a python script that will pull remote state of terraform resources (this is known to work with Azure and Terraform 1.3.0) from a storage blob in Azure. It will use that to generically map those resources to diagram node types. It's rudimentary at this point and only covers a few node types in the resource mappings. But, it will automagically create a dependency diagram from remote state.
If your resources have tags or other metadata that indicate any information for data or workflows that would be good to diagram, you could alter the script to look to include those in the edges as well/in place of a simple dependency graph which is what this currently generates.
Assuming you have remote state stored in an Azure storage blob, just fill in the related fields at the bottom with your details, update the resource type mappings as needed and give it a run.
Beta Was this translation helpful? Give feedback.
All reactions