State locking and how to handle it

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave “+1” or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

cdktf & Language Versions

cdktf --version
0.0.13-pre.2f0b966cb25b6dc5066ee1551fdb32ff47a9c0fd

Affected Resource(s)

State and state locks

Expected Behavior

A way to escape a leaky abstraction of Terraform, directly with cdk-tf tooling. I don’t see any way to manage a local state directly with the cdktf cli.

Actual Behavior

I happened to have a state lock because I hard cancelled a deploy. Next deploy failed because of the lock. Manually deleting lock files didn’t really work. The CLI didn’t suggest any way to resolve the issue (I think Terraform actually helps you resolve locked states because of mistakes). I’m wondering if your aiming (for the future I know that this is alpha software) only for experienced Terraform devs or if this will be a tool that can fully abstract that it’s all Terraform under doing the hard work (like Pulumi does). I’m really missing state commands like the ones in Terraform.

Steps to Reproduce

Hard cancel a deploy (with a local state) and try to deal with the lock.

[akazakou-incomm]

Hey. I’m using cdktf plan in CI and each time it locking state for all CI jobs. Can I disable locking? Seems that -lock=false will not work with cdktf ?

[logusgraphics]

For anyone encountering this issue. I went to the DynamoDB table where the locks are stored and remove the lock manually. That helped me re-run cdktf deploy <stack> successfully.