I've been experimenting with alternative pipeline syntaxes. One example is using Graphviz graph files as an execution plan for software deployments. You can se

I've been experimenting with alternative pipeline syntaxes. One example is using Graphviz graph files as an execution plan for software deployments. You can see a graph here: https://github.com/samsquire/mazzle/blob/master/docs/architecture.tb.png https://github.com/samsquire/mazzle/blob/master/docs/archite... I wrote code with networkx to parse this graph dot file and then follow the plan topologically, spinning up packer, terraform, bash scripts, compilation and so on. It also executes graph nodes in parallel where it can. I talk about it here https://devops-pipeline.com/ https://devops-pipeline.com/ My problem with bash pipelines is passing data along and referring to previous steps' data. You kind of need to enrich the data that goes along the pipeline. In my use case, I need to pass along outputs from previous instantiations.