←back to thread

374 points x0z | 5 comments | | HN request time: 0.355s | source
1. b0a04gl ◴[] No.44434340[source]
what if we can make these diagrams synchronized with reality. you need the diagram to pull from the same source of truth as your actual infrastructure - whether that's terraform state, kubernetes manifests, or service discovery. that way diagrams become less historical artifacts and more of living documentation
replies(3): >>44434366 #>>44434921 #>>44437220 #
2. x0z ◴[] No.44434366[source]
That's a great thought, I'd need to make some kind of translation between manifests and the json, getting knowledge of those relationships might be tricky? Service discovery is another route, would hate to get someones IT department angry for aggressive port scanning though lol
3. jamesponddotco ◴[] No.44434921[source]
Cloudcraft[1][2] can do that with your cloud provider, AWS or Azure. As a bonus, the diagrams also look quite cool.

[1]: https://www.cloudcraft.co/

[2]: I’m part of the Cloudcraft team at DataDog, so obviously, I’m biased.

replies(1): >>44434995 #
4. x0z ◴[] No.44434995[source]
I absolutely love cloudcraft, full disclosure one of our team at work wanted to use it, but we're a public sector org(no money), so I threw this together for him
5. oddlama ◴[] No.44437220[source]
I've written something like this for NixOS a while back [1], which generates infrastructure diagrams directly from the source of truth (albeit not as pretty as isoflow). I'm sure this could be applied to other declarative tech stacks aswell!

[1]: https://github.com/oddlama/nix-topology