IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

Improve the considerations for a possible deprecation of the dynamoDB locking

Browse Source 
Signed-off-by: yottta <andrei.ciobanu@opentofu.org>
This commit is contained in:
yottta 2025-02-17 09:42:51 +02:00
parent d94c599ba0
commit 13a115a02b
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
rfc/20250211-s3-locking-with-conditional-writes.md
View File

@ -125,7 +125,9 @@ But if both locks are enabled (`use_lockfile=true` and `dynamodb_table=<actual_t
* Do we want to provide the option to have the lock objects into another bucket? This will break the feature parity.
### Future Considerations
If this feature will prove to have a high adoption rate, later, we might consider to deprecate the DynamoDB locking mechanism.
Later, DynamoDB based locking might be considered for deprecation once (at least) the following are true:
* Conditional writes are implemented in the majority of the S3 compatible services.
* The adoption rate for the new S3 based locking will be high enough to not affect the existing users.
## Potential Alternatives
Since this new feature relies on the S3 conditional writes, there is hardly other reliable alternative to implement this.