IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-02-25 18:45:20 -06:00
Code Issues Packages Projects Releases Wiki Activity

website: v1.4 upgrade guide more guidance on who is affected by the provider cache change

Browse Source
This commit is contained in:
Omar Ismail 2023-03-09 11:23:20 -05:00 committed by GitHub
parent 32f151f20b
commit bea8ad355c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/language/upgrade-guides/index.mdx
View File

@ -10,18 +10,20 @@ description: Upgrading to Terraform v1.4
Terraform v1.4 is a minor release in the stable Terraform v1.0 series.
Terraform v1.4 honors the [Terraform v1.0 Compatibility Promises](https://developer.hashicorp.com/terraform/language/v1-compatibility-promises), but there are some behavior changes outside of those promises that may affect a small number of users. Specifically, the following updates may require additional upgrade steps:
* [Provider caching during `terraform init`](#provider-caching-during-terraform-init)
* **Important** [Provider caching workflow change during `terraform init`](#provider-caching-during-terraform-init)
* [Hostname interpretation during `terraform init`](#hostname-interpretation-during-terraform-init)
See the full [changelog for more details](https://github.com/hashicorp/terraform/blob/v1.4/CHANGELOG.md). If you encounter any problems during upgrading which are not by this guide, or if the migration instructions don't work for you, please start a topic in [the Terraform community forum](https://discuss.hashicorp.com/c/terraform-core/27) to discuss it.
## Provider caching during terraform init
**_This change affects those who rely upon global provider caching and not the dependency lock file._**
`terraform init` now ignores entries in the optional global provider cache directory unless they match a checksum already tracked in the current configuration's dependency lock file.
Before this change Terraform could not determine the full set of checksums to include in the lockfile when installing a new provider for the first time. Now it can. Once the lock file has been updated to include a checksum covering the item in the global cache, Terraform will then use the cache entry for subsequent installation of the same provider package.
For more details and how to keep using the prior incorrect behavior, please see the [documentation](/cli/config/config-file#allowing-the-provider-plugin-cache-to-break-the-dependency-lock-file).
For more details and how to keep using the prior undesirable behavior, please see the [documentation](/cli/config/config-file#allowing-the-provider-plugin-cache-to-break-the-dependency-lock-file).
## Hostname interpretation during terraform init