Terraform 'Error: Inconsistent dependency lock file' / 'Provider produced inconsistent final plan' - how do I resolve them?

Cause: The two messages are different problems. (1) Dependency lock file: Terraform records the provider versions and package checksums it selected in .terraform.lock.hcl. If the configuration's provider requirements no longer match the lock file (for example you changed a version constraint or added a provider without re-running init), or an installed package matches none of the recorded checksums (often because the lock was created on another operating system or CPU, or via a mirror that only supplies checksums for one platform), Terraform stops. (2) 'Provider produced inconsistent final plan' (and the related 'inconsistent result after apply') is raised when a provider returns values at apply time that differ from what it planned; HashiCorp's provider-development docs describe such consistency rules as the provider's responsibility, for example by marking values as unknown in the plan. This is typically a provider bug rather than a mistake in your configuration. Fix: 1. Lock file: run terraform init. If you deliberately changed constraints and want the newest allowed versions, run terraform init -upgrade, review the diff in .terraform.lock.hcl, and commit it. HashiCorp recommends keeping the lock file in version control and reviewing provider changes like code changes. 2. Multi-platform teams or CI on a different OS: pre-populate checksums with terraform providers lock -platform=linux_amd64 -platform=darwin_arm64 -platform=windows_amd64 (repeat the flag per platform you use), then commit the file. If you install from a mirror, omit the mirror options when locking so that the publisher's signed checksums are recorded. 3. Do not hand-edit hashes or delete checksums to silence a mismatch unless you have verified the provider source; a checksum mismatch can mean the package differs from what was originally selected. 4. For old Terraform v1.0 or earlier with stale entries from removed providers, running init with a newer Terraform version tidies up the lock file. 5. Inconsistent final plan: rerun terraform plan and apply, since transient cases sometimes clear. Then upgrade the provider to its latest release (terraform init -upgrade), check the provider's issue tracker for the resource named in the error, and report it with the full error text if it persists. Where possible avoid values in your configuration that are only known after apply in the failing argument. Verify: terraform init completes without lock errors, terraform providers shows the expected versions, and plan followed by apply completes. Run terraform init on each platform or CI runner once to confirm no new lock changes are produced. Sources: https://developer.hashicorp.com/terraform/language/files/dependency-lock https://developer.hashicorp.com/terraform/cli/commands/providers/lock https://developer.hashicorp.com/terraform/plugin/framework/resources/plan-modification