framework: Fix MoveResourceState
tests
#382
Merged
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.
Related Issue
Supersedes #367, fixes for hashicorp/terraform-plugin-framework#1193
Description
The identity that is part of the
MoveResourceState
state test was reliant on the data passing throughReadResource
without erroring. Earlier versions of Terraform that don't support identity were not sending this data, which resulted in theRead
for the resource returning a null identity.As of hashicorp/terraform-plugin-framework#1193, that is no longer valid. Resources must always produce an identity during
Read
, typically using the state and a remote system.Since the move resource test is really just taking data from state and putting it into identity, we can just do this during
Read
as well, since we have no remote system. The check for null is really just to respect that the underlying test assertions inMoveResourceState_identity
want to test the logic ofMoveResourceState
and notReadResource
, but we don't want to do a "no-refresh" test step.Rollback Plan
Changes to Security Controls
No