Revise boolean preservation test to trigger Update via priority #1164
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.
Change summary
This PR updates the acceptance test for preserving optional boolean fields in the
headerblock to ensure it actually exercises theUpdate()path.Previously, the test modified only the
namefield — which causes a resource recreation due to identity semantics in Terraform (nameis used as the identity key in aTypeSet). As a result, the test didn’t confirm thatignore_if_setwas preserved during an update, defeating the purpose of the fix introduced in #1142.To correct this:
prioritynameremains constant to ensure an in-place updateignore_if_setis explicitly verified before and after the updateOutcome:
Update()is invokedignore_if_setis preserved as expectedAll Submissions: