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
Would need some extra data for the nodes, but as I understand it this should be relatively easy to add. This would require policy-machinery work to serialize things in a JSON format instead of a DOT file.
The text was updated successfully, but these errors were encountered:
Something @Boomatang chatted about a few weeks back: including resource status/conditions in topology. I think we'd be approaching the breaking point of using the DOTfile to serialize at that point, so we may want to serialize the graph in some sort of JSON/YAML format too, in addition to the dotfile. This'd help us visualise status/conditions in the topology view, which'd be super sweet.
After we spoke about this I did a little bit more looking into it. At the time I was almost sure the exporting of JSON or YAML would be relativity straight forward. However that is not true, it was the github.com/goccy/go-graphviz library that had the multiple export opinions. We had to switch this library out as it was not thread safe and cause issue. It was switch out for github.com/emicklei/dot.
Policy topology: add status/conditions
Would need some extra data for the nodes, but as I understand it this should be relatively easy to add. This would require policy-machinery work to serialize things in a JSON format instead of a DOT file.
The text was updated successfully, but these errors were encountered: