-
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
Remove dynamodb table and legacy role for state access #9121
Conversation
Terraform Plan Summarymodernisation-platform-account |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🔥
A reference to the issue / Description of it
#8345
How does this PR fix the problem?
Prior to this PR we offered a role in the Modernisation Platform repository for S3 state locking.
Our previous use of state locking required access to a DynamoDB table in order to place and release state locks. To access this DynamoDB table our users assumed a role in the same account as the table.
Now that we have implemented native state locking we no longer require this DynamoDB table, nor do we require the role that users would assume to access it.
This PR will require any customers who have not done so already to either delete their
.terraform
directory locally if they conduct local plans of their work, or alternativeterraform init --reconfigure
if appropriate.How has this been tested?
Tested through CI, tested locally with
developer
credentials to a small number of accounts in modernisationplatform-environments.Deployment Plan / Instructions
Deploy through CI
Potential impact to customers who do not undertake a deletion of any local
.terraform
directory created with legacy configuration to assume the now-deleted role.Checklist (check
x
in[ ]
of list items)Additional comments (if any)
https://developer.hashicorp.com/terraform/cli/commands/init#backend-initialization