Terraform v1.0 Is Out
terraform.io
terraform.io
I know that this desire conflicts with the submission guideline to avoid modification of the original title unless misleading. I understand that this technique can sometimes foster curiosity, and cause users to follow links and learn about new things. Still, I often read submissions and even websites that assume a level of familiarity that act as a barrier to followup simply because I miss a useful connection.
I also recognize that this may be perceived as mere laziness on my part, and you're right, it is. Suggested title:
Terraform v1.0 Release: Allows users to declaratively describe infrastructure configuration on multiple public clouds.
Alternatively, a submission content tagging scheme could work, but that introduces other challenges. [ ML content tagging system, anyone? ]
In this specific instance, terraform is not exactly an obscure piece of tech. Do you really think your suggested title is an improvement?
Do you consider my suggested title editorializing? If so, how?
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.
(other post has more comments)
ty