I mean this as a constructive complaint, not just for this post, but many posts on HN: I do wish the titles of submissions included some context that would clue me into the nature of the product, service, or meaning of the submission. I do not fault the submitter.<p>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.<p>I also recognize that this may be perceived as mere laziness on my part, and you're right, it is. Suggested title:<p>Terraform v1.0 Release: Allows users to declaratively describe infrastructure configuration on multiple public clouds.<p>Alternatively, a submission content tagging scheme could work, but that introduces other challenges. [ ML content tagging system, anyone? ]
I recommend breaking out your terraform code into separate folders and calling them "components". Write a wrapper around the terraform script to pass in -var-file which uses an argument called ENVIRONMENT that you pass to the wrapper. I think the built in support for modules is less useful for what you actually want to do because you end up with variables spread between variables.tf, outputs.tf files.<p>I use a tool I wrote to layer my infrastructure with layers called components and I configure it with a Graphviz file.<p>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.<p>Here's an example of a graph generated from graphviz file:
<a href="https://github.com/samsquire/mazzle/blob/master/docs/architecture.png" rel="nofollow">https://github.com/samsquire/mazzle/blob/master/docs/archite...</a><p>This graph brings up a hashicorp vault server, Java application, bastion proxy etc.<p>here's the graphviz file: <a href="https://github.com/samsquire/mazzle-starter/blob/master/architecture.dot" rel="nofollow">https://github.com/samsquire/mazzle-starter/blob/master/arch...</a><p>It describes the ordering of the infrastructure, the invocation of Ansible, packer, shell scripts to set up vault etc.<p>The idea is to be able to bring up a new environment by changing one parameter. There's a React GUI too.<p><a href="https://devops-pipeline.com" rel="nofollow">https://devops-pipeline.com</a>
dupe: <a href="https://github.com/hashicorp/terraform/releases/tag/v1.0.0" rel="nofollow">https://github.com/hashicorp/terraform/releases/tag/v1.0.0</a><p>(other post has more comments)