Skip to content

Conversation

@philippschulte
Copy link
Member

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 name attribute, which triggered a delete-and-recreate (due to implicit ForceNew behavior), 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:

  • Keeps the backend name constant
  • Changes the connect_timeout field, which triggers a real Update() call
  • Verifies that all optional boolean fields are preserved as expected

Outcome:

All Submissions:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?

@philippschulte philippschulte requested a review from a team as a code owner December 2, 2025 18:51
@philippschulte philippschulte added the Skip-Changelog Skip changelog build check label Dec 2, 2025
@philippschulte philippschulte merged commit 673731c into fastly:main Dec 3, 2025
23 checks passed
@philippschulte philippschulte deleted the pschulte/backend-update-preserve-bools branch December 3, 2025 02:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Skip-Changelog Skip changelog build check

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants