Hello
If a customer uses terraform 12 and generates his resources and the corresponding state file. Now he wants to use terraform 13. He has updated the tf files following the guidance at https://www.terraform.io/upgrade-guides/0-13.html. Can he be able to successfully use the terraform 12 state file for the future terraform executions. Asking because occassionally we have observed terraform failed to initialize errors even though the said providers are available on the local machine. If the customer tries to directly try terraform 13 it works flawlessly, its failing only in the upgrade path in the tf initialization step. Below is the error message (and its not consistent):
Initializing modules…
bastion in modules/bastion
coordinator in modules/coordinator
network in modules/network
support in modules/support
utility in modules/utility
worker in modules/worker
Initializing provider plugins...
Finding latest version of -/local...
Finding latest version of -/null...
Finding latest version of -/oci...
Finding latest version of -/tls...
Finding latest version of hashicorp/tls...
Finding latest version of hashicorp/local...
Finding latest version of hashicorp/null...
Finding latest version of hashicorp/oci...
Installing hashicorp/oci v4.4.0...
Installed hashicorp/oci v4.4.0 (unauthenticated)
Installing -/oci v4.4.0...
Installed -/oci v4.4.0 (unauthenticated)
Installing hashicorp/tls v2.0.1...
Installed hashicorp/tls v2.0.1 (unauthenticated)
Installing hashicorp/local v1.4.0...
Installed hashicorp/local v1.4.0 (unauthenticated)
Installing hashicorp/null v2.1.2...
Installed hashicorp/null v2.1.2 (unauthenticated)
Warning: Interpolation-only expressions are deprecated
on compute.tf line 3, in data "null_data_source" "vpus"
3: block_vpus = "${var.block_volume_high_performance ? 20 : 0}"
Terraform 0.11 and earlier required all non-constant expressions to be
provided via interpolation syntax, but this pattern is now deprecated. To
silence this warning, remove the "${ sequence from the start and the }"
sequence from the end of this expression, leaving just the inner expression.
Template interpolation syntax is still used to construct strings from
expressions when the template includes multiple interpolation sequences or a
mixture of literal strings and interpolations. This deprecation applies only
to templates that consist entirely of a single interpolation sequence.
(and 238 more similar warnings elsewhere)
Warning: Quoted type constraints are deprecated
on variables.tf line 172, in variable "OELImageOCID"
172: type = "map"
Terraform 0.11 and earlier required type constraints to be given in quotes,
but that form is now deprecated and will be removed in a future version of
Terraform. To silence this warning, remove the quotes around "map" and write
map(string) instead to explicitly indicate that the map elements are strings.
(and 3 more similar warnings elsewhere)
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider -/local:
provider registry.terraform.io/-/local was not found in any of the search
locations
/home/orm/remote/providers13
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider -/null:
provider registry.terraform.io/-/null was not found in any of the search
locations
/home/orm/remote/providers13
Error: Failed to query available provider packages
Could not retrieve the list of available versions for provider -/tls: provider
registry.terraform.io/-/tls was not found in any of the search locations
/home/orm/remote/providers13