Complete procedures with a way back.

Terraform Error: Provider configuration not present means state still associates one or more managed resource instances with a provider configuration address that the current root module can no longer supply. The missing object may be a deleted child-module provider block, a removed alias, an absent module call, or a changed provider source. Repair the execution context before planning any infrastructure change.

Terraform Error acquiring the state lock means the configured backend refused a potentially state-writing operation because another lock exists or the lock service is unavailable. The safe response is to identify the exact backend, workspace, lock owner, and active run before considering force-unlock.

Compare protected refresh-only and normal plans, classify authority and impact, contain incidents, accept reality in HCL or restore intent through a saved plan, and verify full convergence without automatic apply.

Adopt existing provider objects through Terraform 1.15 import blocks, stable addresses, optional reviewed generated HCL, import-only saved plans, protected state, and a mandatory empty post-import plan.

Design a real module contract, keep provider and backend ownership in environment roots, pin releases, protect sensitive state in versioned encrypted S3 storage, use Terraform 1.15 native lockfiles, and rehearse upgrades and recovery.