Skip to content

Conversation

@bogsi17
Copy link
Contributor

@bogsi17 bogsi17 commented Jun 11, 2025

  • The state locking now works via the use_lockfile parameter instead.
  • Everything DynamoDB-related can thus be removed. Resources, Permissions and documentation

Jira-Issue: MAV-1260

* The state locking now works via the `use_lockfile` parameter instead.
* Everything DynamoDB-related can thus be removed. Resources, Permissions and documentation

Jira-Issue: MAV-1260
@bogsi17 bogsi17 requested review from a team as code owners June 11, 2025 09:06
@sonarqubecloud
Copy link

@bogsi17 bogsi17 added the infrastructure Related to infrastructure changes label Jun 11, 2025
Copy link
Contributor

@thomasleese thomasleese left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where is the lock file stored, in the S3 bucket?

@bogsi17
Copy link
Contributor Author

bogsi17 commented Jun 11, 2025

Where is the lock file stored, in the S3 bucket?

@thomasleese Yes, and it only exists if the state is currently locked.

@bogsi17 bogsi17 merged commit fbc6366 into main Jun 11, 2025
13 checks passed
@bogsi17 bogsi17 deleted the remove_dynamodb_locking branch June 11, 2025 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

infrastructure Related to infrastructure changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants