Revise boolean preservation test to trigger Update via connect_timeout #1162
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 boolean preservation acceptance test originally introduced in #1133 to ensure that it reliably exercises the
Update()path of the backend resource.Previously, the test changed only the
nameattribute, which triggered a delete-and-recreate (due to implicitForceNewbehavior), rather than an in-place update. As a result, the test did not verify that boolean fields (use_ssl,ssl_check_cert, etc.) were preserved during updates — the primary goal of #1133.To correct this, the updated test now:
nameconstantconnect_timeoutfield, which triggers a realUpdate()callOutcome:
All Submissions: