docs: add v3 upgrade troubleshooting and index guide links - #1809
docs: add v3 upgrade troubleshooting and index guide links#1809Angel-4903 wants to merge 1 commit into
Conversation
Add a Troubleshooting section to the v3 upgrade guide covering the 'Blocks of type "kubernetes" are not expected here' error introduced by the SDKv2 -> Terraform Plugin Framework migration, with a block-to-attribute mapping table and a v2 pinning fallback (hashicorp#1637). Also document the macOS OCI registry keychain login failure and its workarounds (hashicorp#989). Create templates/guides/v3-upgrade-guide.md as the generation source for the existing docs/guides/v3-upgrade-guide.md, and link both upgrade guides from the provider index template and rendered index page. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Angel Raphael seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
1 similar comment
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Angel Raphael seems not to be a GitHub user. Have you signed the CLA already but the status is still pending? Recheck it. |
1 participant
Add a Troubleshooting section to the v3 upgrade guide covering the 'Blocks of type "kubernetes" are not expected here' error introduced by the SDKv2 -> Terraform Plugin Framework migration, with a block-to-attribute mapping table and a v2 pinning fallback (#1637). Also document the macOS OCI registry keychain login failure and its workarounds (#989).
Create templates/guides/v3-upgrade-guide.md as the generation source for the existing docs/guides/v3-upgrade-guide.md, and link both upgrade guides from the provider index template and rendered index page.
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
Description
Acceptance tests
Release Note
Release note for CHANGELOG:
References
Community Note