Reusable GHA for Terraform deploy #323
Conversation
| storage_account_name = "tfstaterv2024" | ||
| container_name = "rv-tfstate" | ||
| key = "dev.terraform.tfstate" | ||
| use_oidc = true |
There was a problem hiding this comment.
these are just auto formating changes
| storage_account_name = "tfstaterv2024" |
There was a problem hiding this comment.
Assuming these are for each of the different dev environments?
There was a problem hiding this comment.
thats correct! so with TF you can store the configuration state files either locally on our computers or a in a central location. these config files basically create and update these files in a global AZ Resource Group in the same account subscription. the benefit of separating them out into individual files like this is so we can use the -backend-config=config/${{ inputs.deploy-env }}.config flag in the terraform cli. We are no using that here in a reusable GHA:
In the future however, I would like to research and find out if this is for sure the best and most appropriate way of doing this but for now, this allows for a bunch of flexibility.
💯 ! Getting very close for sure. |
Description
This is so we can finally automate the Terraform apply process with Github Actions rather than from my personal command line. This will be added to the combined deployment.
Screenshots (if applicable)
Related Issues
[Link any related issues or tasks from your project management system.]
Checklist