generated from ministryofjustice/template-repository
-
Notifications
You must be signed in to change notification settings - Fork 290
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
Replace Terraform DynamoDB state locking with native state locking #8345
Labels
Comments
dms1981
added
documentation
enhancement
New feature or request
terraform
Pull requests that update Terraform code
labels
Oct 25, 2024
4 tasks
Believe this is now available |
Prior issues on state locking for reference: |
This was referenced Jan 21, 2025
This was referenced Jan 22, 2025
Draft
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
User Story
As a Modernisation Platform Engineer
I want to implement Terraform native state locking
So that I don't need to use DynamoDB for state locking
Value / Purpose
In Terraform 1.10.* Hashicorp will implement native state locking that is not reliant on DynamoDB tables.
The present use of DynamoDB for state locking introduces friction for our customers when stale state locks persist and require removal. Further to this we have to assume a role in the MP account in order to access the DynamoDB table.
By using native state locking we can reduce the amount of friction customers get by needing us to remove stale state locks, and we can simplify both our terraform configuration and our guidance on running local plans by removing the steps needed to assume a role in the main MP account during
terraform init
Useful Contacts
No response
Additional Information
No response
Definition of Done
The text was updated successfully, but these errors were encountered: