Skip to content

fix keyring bug - #1714

Open
jaylonmcshan19-x wants to merge 1 commit into
hashicorp:mainfrom
jaylonmcshan19-x:fix-keyring-state-upgrade
Open

fix keyring bug#1714
jaylonmcshan19-x wants to merge 1 commit into
hashicorp:mainfrom
jaylonmcshan19-x:fix-keyring-state-upgrade

Conversation

@jaylonmcshan19-x

Copy link
Copy Markdown
Contributor

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

This pr Fixes the "Provider produced invalid plan" error that occurs when upgrading from provider v2.x to v3.x with keyring attribute set to empty string or null.

the pr normalizes empty string keyring values to null during state migration
from v2 to v3 to match user configurations.

Acceptance tests

  • Have you added an acceptance test for the functionality being added?

Release Note

Release note for CHANGELOG:

...

References

#1695

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

@jaylonmcshan19-x
jaylonmcshan19-x requested a review from a team as a code owner October 27, 2025 18:14
@kimxogus

kimxogus commented Jan 2, 2026

Copy link
Copy Markdown

This fix is critical to my case. Hope to be released asap 👍

@phyzical

phyzical commented Jan 8, 2026

Copy link
Copy Markdown

worth noting all this pr does is forces a default value of keyring = "" so simply add that to keep getting on with your day

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants