Create New Skeleton "skeleton-tf-root-module"

[mcdonnnj]

💡 Summary

Consider creating a new skeleton repository that either descends from cisagov/skeleton-generic or from this repo. This would focus on Terraform code that is not designed for reuse as opposed to the goal of this skeleton.

Motivation and context

We have been using this skeleton for anything Terraform related and it has worked, but the workflows for Terraform modules and Terraform deployments have core differences. Creating a new skeleton-tf-root-module repository would allow Terraform deployment related standards to be represented in a skeleton instead of needing to look across existing deployment repositories to figure out what files need to be added (at minimum) as well as how things look across such projects in our organization.

Implementation notes

Ideally once this new skeleton is created we would, over time, migrate any Terraform code repositories that are not designed to be importable modules to descend from this new skeleton. Then any future Terraform with similar design goals would start from the new skeleton instead of this repository.

Acceptance criteria

• New repository is created
• Dev team signs off on the Initial Commits Pull Request
• (OPTIONAL) Existing Terraform deployment repositories are migrated to use this new skeleton

[jsf9k]

The handling of default tags by the actual Terraform module and the example code in #49 highlights another place where cisagov/skeleton-tf-module and the new skeleton repository that @mcdonnnj is proposing would differ. I was a little meh about the need for a separate repo, but this has pushed me toward heartier support of this addition.

[mcdonnnj]

Updated the proposed skeleton name to mirror the language used by Terraform as was pointed out to me by @jsf9k 🍻