The lock client never stores absolute times in DynamoDB -- only the relative "lease duration" time is stored in DynamoDB. The way locks are expired is that a call to acquireLock reads in the current lock, checks the RecordVersionNumber of the lock (which is a GUID) and starts a timer...
awsbackendterraformdynamodbs3-bucketlockingtfstateterraform-modulesaws-dynamodbdynamodb-tableterraform-moduleremote-stateterraform-statehcl2 UpdatedJan 1, 2025 HCL minio/dsync Star397 Code Issues Pull requests A distributed sync package. distributed-systemscloud-storagelockingquorumdistributed-locksobject-storage...
How DynamoDB locking works When you runterragrunt applyorterragrunt destroy, Terragrunt does the following: Create theterragrunt_lockstable if it doesn't already exist. Try to write an item to theterragrunt_lockstable withStateFileIdequal to thestate_file_idspecified in your.terragruntfile. This ...
DynamoDB Lock Client is an open-source project that will be supported by the community. Please create issues in the GitHub repository with questions. Use cases A common use case for this lock client is: let's say you have a distributed system that needs to periodically do work on a given...
table_name: (Optional) The name of the table in DynamoDB to use to store lock information. Default: terragrunt_locks. max_lock_retries: (Optional) The maximum number of times to retry acquiring a lock. Terragrunt waits 10 seconds between retries. Default: 360 retries (one hour). aws_profi...