I've got a similar project which takes a diagram of your infrastructure, such as [1] and runs the diagram to build your devops infrastructure [2].
[1]: http://devops-pipeline.com/architecture.tb.png [2]: http://devops-pipeline.com/
Diagram as Code
21–30 of 77 posts
Re: Diagram as Code
#22When I first read this I thought this did the inverse of what it actually does. Let you interactively draw out diagrams then it would generate the boilerplate code to achieve that diagram.
If we had a decent diff tool for visual elements, then a whole lot of tools would be practical, including the one you suggest.
Certainly a lot of the building blocks for such a system now exist.
Re: Diagram as Code
#23I have been thinking about using this for some diagrams, but whats been on the back of my mind since I heard about it is how to combine it with Terraform, or Troposphere, and have your infrastructure as code also draw the diagrams automatically.
Re: Diagram as Code
#24I was hoping this tool would support directionality/sequencing of nodes. A tool I've used in the past is SequenceDiagram.org for diagraming a sequence of service calls. While a bit old-school, it's good for its purpose. I've also used Whimsical[0] to model flows and graph-like relationships. It's got the added benefit of allowing multiple users to view and edit the same document. Whimsical is still my favorite tool r…
What about mermaid-js? Here's a sequence diagram example: https://mermaid-js.github.io/mermaid-live-editor/#/edit/eyJj...
Re: Diagram as Code
#25Earlier quoted context omitted.
The focus would make sense to me if, say, it exported to initial terraform templates or something like that.
I’d prefer to avoid text blob artifacts if this was being used at work with plenty of text blobs to babysit already IMO the end days for TF and YAML engineering are close, at least for new work It’s all HTTP APIs. Build a web UX and store the state in a DB. SRE/ops people ...at work just use the methods everyone else does Unless the company still has hardware, cloud ops/SRE is just making their lives harder to be dif…
There is significant value in text blob workflows.
Requiring the definition of everything that makes up your stack to be stored in a format that is not text adds complexity to the disaster recovery process, not to mention mutation, diffing, reviewing, approving, promoting, etc.
For places where a single environment that is updated in place and requires little/no approval to do so, sure. Personally I really like textual definition of infrastructure and configuration, and disagree that it is end days for them.
Re: Diagram as Code
#26Sent this to a few people at work and it spread pretty quickly. We all love it!
Re: Diagram as Code
#27This is great. Code needs to replace more drag n drop tools, at the very least to give people options.
Re: Diagram as Code
#28I was recently looking for something similar, allowing me to draw network diagrams using text or code. I came across [0] which looks great, but has some rough corners and seems to be abandoned by he author. Does anyone have any other recommendations for more bare-metal oriented topologies?
Re: Diagram as Code
#29I just created a Dockerfile to run: https://github.com/skhaz/diagrams
Re: Diagram as Code
#30It seems to be hyperfocused on system architecture diagrams. There are some other kinds of diagrams would we like to draw that’s not system architecture diagrams, eg: - algorithms - decision trees - UML/ER Diagrams Mermaid (JS) helps draw quality diagrams quickly - more than system architecture diagrams. It would have been perfect if the development cycles that went here was used to create Mermaid templates instead.…
Nice suggestion. The headline appears misleading to me, I like what I see there, but it's really "Diagram as Config" not source code generally.