terraform fmt- Reformat your configuration in the standard style.terraform init- Prepare your working directory for other commandsterraform validate- Check whether the configuration is validterraform plan- Show changes required by the current configurationterraform apply- Create or update infrastructure, can add-auto-approveflag to not having to confirm changes.terraform destroy- Destroy previously-created infrastructure, can add-auto-approveflag to not having to confirm changes.
terraform state needs to stored remotely in aws s3. To do that,
- we are creating s3 and dynamodb for different for all projects.
- these backend configs will be then passed to respective terraform repos
- the main creates a state remote for all projects.
- simply add config values to
backend.hclfile in respective project.
first just create the infrastructure, that is, module "tf-state" using terraform init and then terraform apply.
the main's state can be commited to github. not to be shared with others. keeping state in remote s3 bucket and dynamodb still has a possibility being deleted accidently.
If in future we want to store state for this one also in remote s3, add backend "s3" {} to backend. add backend.hcl file. run yarn tf-init, which will use backend.hcl configs. you will given option to send local stat
57D1
e to remote, do make sure to send it.
for the rest of modules, just create the infrastructure using terraform apply. use names and region used to generate s3 bucket and dynamodb table in corresponding project's backend.hcl files.
ALSO, notice that the s3 backend can be in a different region from the infrastructure. backend.hcl has required argument for region. so lets keep all the project's s3 backends in one region only.
the module "tf-state" Has all the other files, do not delete, like ever.
I can also create admin user profiles from here for different projects. #TODO