What is a lock state?

Lock state in configuration management systems (e.g., Terraform) is a mechanism that prevents multiple users or processes from changing the infrastructure simultaneously. It ensures atomicity of operations, guaranteeing that only one process can modify the infrastructure state described in the state file at any given time.

Main points:

• Purpose: To avoid collisions and state inconsistencies that occur when working on the same infrastructure simultaneously.
• Operation principle: When a process begins to change the state, it sets a lock. Other processes attempting to access the state wait until this lock is released.
• Storage location: The lock mechanism is often integrated with the backend where the state file is stored (e.g., S3, Consul, etcd). Locking can be implemented at the storage level.
• Types of locking (in Terraform):
  • Advisory Lock: A lock that the client must respect, but the system does not enforce.
  • Mandatory Lock: A lock that is enforced by the system.

Example of backend configuration in Terraform with lock support:

terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "path/to/state.tfstate"
    region         = "us-east-1"
    dynamodb_table = "terraform_locks" // DynamoDB table for lock mechanism
    encrypt        = true
  }
}

In this example, the DynamoDB table terraform_locks is used to manage lock states for the S3 backend.