-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flatten TF module structure via .tfvars
/.tfbackend
#980
Conversation
a8bdd8d
to
2f0e09c
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This module restructuring clobbers the existing state, but I don't really want to fill up the template with a bunch of |
As an example of how to use these environments, navigate to the
If you then try switch to production (not that you should really be doing that outside of CI/CD), the CLI will instruct you to call
|
dd4d37a
to
7602118
Compare
Rebased on |
@jvisker have we talk about this in the cloud guild yet? Are we still discussing it? Do we need to update an ADR before merging? |
Updated docs. That needed to happen. Also renamed |
Another tiny reason to rename |
570809e
to
f27ecde
Compare
.tfvars
/.tfbackend
, update to TF v1.5.3.tfvars
/.tfbackend
Rebased on |
… local backend This makes it harder to do the wrong thing. With this change, we avoid a potential footgun when developers use `terraform init` instead of `terraform init -backend-config=dev.s3.tfbackend`. This isn't a functional change because we were already using encryption on everything in our state buckets.
Docs needed to be updated either way. I know we've done some bikeshedding on the directory name before. I didn't previously care whether it was called terraform/, iac/, terraform-iac/ or anything else. Nowadays, I have a tiny reason to prefer the name terraform/: it plays nicely with automatic folder icons. The other options don't.
f27ecde
to
0bc6d66
Compare
Closing in favor of #1247. |
Using
.tfvars
and.tfbackend
files, we can flatten our TF modules.