You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The lock_table property (which by the way I now realize is deprecated in favor of the dynamodb_table property!) specifies a DynamoDB table, but that table will have one row or entry for each unique Terraform state. Therefore, as long as you keep the Terraform states in your various environments separate, then you'll have a unique lock on each and can work in parallel as you desire.
I suspect that even if you use the same DynamoDB table for locks, if the key parameter is different, then the lock will be different too. Since you have different state files for each environment, and therefore different key values, you shouldn't be seeing lock contention.
I noticed that lock_table is hard coded. Why not have it based on the environment (prd, dev, qa) so that you can work on these in a parallel fashion?
The text was updated successfully, but these errors were encountered: