mazzle VS terraform-ls

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/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/

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.

I use Graphviz dot syntax to configure entire cloud computing environments in the order they must be built. This is pipelines as code and infrastructure as code

It's very powerful! Not every organisation can bring up an entire environment with one command.

Here is a executable diagram of a build worker cloud nodes, Kubernetes, consul, vault, Debian package server, Java app, SSH bastion, Prometheus, grafana, DNS and security groups.

https://github.com/samsquire/mazzle/blob/master/docs/archite...

The tool also parallelises the build based on the graph so packer builds can run in parallel.

https://devops-pipeline.com/

It also has a GUI but it's not ready for other people to use.

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

Marcin here, one of the OpenTF folks

This repo [0] seems to still be licensed under MPL, so there is no need for an immediate action, but if there is a willingness in the community to take it over and improve, I see no reason why we wouldn't do it.

[0] https://github.com/hashicorp/terraform-ls

For example my other issue with simple click through URLs to resource documentation pages, this would be a simple solution if the resource documentation URL formatting was done to a standard with the resource names.

I have followed this guide: https://github.com/hashicorp/terraform-ls/blob/main/docs/USAGE.md

As /u/fridgedigga, neither LSP implements renaming. The LSP spec can be found here. I don't know how all of this is wired up. At a minimum, you'll need to add a mapping in service.go and handler. The bulk of work is performed in the handlers.

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

For the LSP, I have never heard of Terraform before but it looks like they have a section on using it with vim/neovim. Not sure if this is already part of what you have tried, but I can't really help more since I have never used it.

This worked, thank you! I found all the cli options here for anyone that needs them.

https://github.com/hashicorp/terraform-ls

These are both fairly limited but you can see every editor (except intellij) uses this under the hood.

I've used them at companies with 300+ terraform repos and have never had much of an issue navigating/understanding TF through Vim.

So, what happens when you run the server from command line and then open your file in Kate? Any difference? Also, is there any command argument for logging and/or debugging the terraform-ls? It might help to find the issue, if any. I found this from the docs.