mazzle-starter VS terraform-lsp

I take advantage of I/O being parallel in Python in my mazzle continuous integration pipeline tool. I'm not sharing mutable state.

I spin up a graph of python Threads and each joins others in a graph. This way we can run graphs in parallel. See this graph - the parts that look like this:

dependency -> {parallel1; parallel2; parallel3} -> postparallel

parallel1, parallel2, parallel3 can run in parallel in a separate python thread because the IO is parallel.

postparallel joins parallel1, parallel2, parallel3 and waits for them all to complete.

Where parallel1-3 is things like ansible, packer (slow), AMI builds, chef runs etc.

https://github.com/samsquire/mazzle-starter/blob/master/arch...

I use a tool I wrote to layer my infrastructure with layers called components and I configure it with a Graphviz file.

My tool, called mazzle (previously devops-pipeline) would run parts of the graph that can run in parallel in parallel. It can also run parts of the build on SSH workers. You bring up the workers at the beginning of the build.

Here's an example of a graph generated from graphviz file: https://github.com/samsquire/mazzle/blob/master/docs/archite...

This graph brings up a hashicorp vault server, Java application, bastion proxy etc.

here's the graphviz file: https://github.com/samsquire/mazzle-starter/blob/master/arch...

It describes the ordering of the infrastructure, the invocation of Ansible, packer, shell scripts to set up vault etc.

The idea is to be able to bring up a new environment by changing one parameter. There's a React GUI too.

https://devops-pipeline.com

Look at terraform-ls vs terraform-lsp. Both can be used with coc.nvim.

Also installed terraform-lsp as its steps.

Also try terraform-lsp and see if it works.