![]() ![]() Whenever you upgrade Terraform, review your provider Sometimes an older version of a provider will not work with a newer Terraform manages provider versions independently of the version of Terraform Project, there is no supported way to revert to using an older state file ![]() Once you use a newer version of Terraform's state file format on a given For most commands, you can disable locking with the "-lock=false" flag, but this is not recommended. Please resolve the issue above and try again. $ terraform apply Error: Error locking state: Error acquiring the state lock: state snapshot was created by Terraform v0.15.0, which is newer than current v0.12.30 upgrade to Terraform v0.15.0 or greater to work with this state Terraform acquires a state lock to protect the state from being written by multiple users at the same time. If you forget, other commands will detect it and remind you to do so if necessary. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. Try running "terraform plan" to see any changes that are required for your infrastructure. Terraform has been successfully initialized! You may now begin working with Terraform. Include this file in your version control repository so that Terraform can guarantee to make the same selections by default when you run "terraform init" in the future. to record the provider selections it made above. Installed hashicorp/aws v2.13.0 (signed by HashiCorp) Terraform has created a lock file. ![]() Installed hashicorp/random v3.1.0 (signed by HashiCorp) - Installing hashicorp/aws v2.13.0. Finding hashicorp/aws versions matching "~> 2.13.0". Finding hashicorp/random versions matching ">= 2.1.2". $ terraform init Initializing the backend. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |