write-only attributes: internal providers should set write-only attributes to null #36824
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
liamcervante
added
the
1.11-backport
radeksimko
added
the
1.12-backport
DanielMSchmidt
previously approved these changes
Apr 2, 2025
jbardin
approved these changes
Apr 2, 2025
|
Wow, thanks for the quick fix @liamcervante 🙏 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have several internal providers that wrap external providers and override functionality. These providers must handle setting write-only attributes to null automatically as Terraform expects this.
The mock provider in the testing framework, the unknown provider in stacks, and the override_resource functionality in the testing framework are all fixed in this PR.
Fixes #36819
Target release: v1.11.4