query: validate identity did not change when schema version does not change #37716
+96
−21
Conversation
This file contains hidden or 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
dsa0x
added
the
no-changelog-needed
dsa0x
changed the title
|
It feels like we're reintroducing something that we explicitly removed in #36989. Are all provider authors onboard? I'm being extra cautious here since there have been multiple incidents related to resource identity validation. |
No. I started an internal discussion on this last week, and would move this back to draft. |
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.
This adds a validation for the resource identity, checking that the identity must not change during the
PlanResourceChange,ReadResource, andApplyResourceChangeRPCs. Any change to the identity should be within theUpgradeResourceIdentityRPC, which always precedes the aforementioned ones.Target Release
1.15.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry