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
As discussed with Antoine on LinkedIn, I think it would be great to add support for any kind of resources.
I mainly use Azure, GCP, Kubernetes providers but I guess it would be enough to have some default display with unsupported resources (my understanding is that you did AWS because you had the use case and the icons in hands) but TF/TOFU providers list is quite long . So a strategy to integrate beautifuly the 80% more used would be nice, but be able to display all kind of resources regardless of their provider would be awesomer
I suppose we can use some kind of regex to display the relevant information even if it's not 100% eye-candy
example:
^(?'provider'[a-z]+)_(?'resourcetype'[a-z_]+)$
Then display those information in the resource square as you do for supported resources but with text ?
The issue is not with the icons, but with summarizing multiple resources, which are related, into one. If we didn't do that it would be a mess, just like most of the other terraform visualizers. We would like to do the things that we do well, and adding other providers would spread our attention too thin.
We will definitely do this though at a later stage, after we've validated our most risky assumptions :)
In case you are wondering, what we are grappling with: How do we turn this project from a "nice to have" into a "must have"
Activity
dant2021 commentedon Mar 6, 2024
Hey,
The issue is not with the icons, but with summarizing multiple resources, which are related, into one. If we didn't do that it would be a mess, just like most of the other terraform visualizers. We would like to do the things that we do well, and adding other providers would spread our attention too thin.
We will definitely do this though at a later stage, after we've validated our most risky assumptions :)
In case you are wondering, what we are grappling with: How do we turn this project from a "nice to have" into a "must have"
snemetz commentedon Mar 27, 2024
When your ready to expand
+1 for GCP support. Even if it is limited to start
Laffs2k5 commentedon Apr 25, 2024
Impressive work this far!
Hope you're also able to support Azure resource in the future :-)
albschi commentedon May 13, 2024
@snemetz @Laffs2k5 GCP and Azure are now supported, and you can give it a try