Migrate data_source_google_compute_global_address.go data source to use direct HTTP rather than a client library - #18465
Conversation
|
Hi there, I'm the Modular magician. I've detected the following information about your changes for commit ba79e1e: Diff reportYour PR generated the following diffs in downstream repositories:
Test reportAnalytics
Affected Service Packages
Step 1: Replaying Mode Action takenFound 2 affected test(s) by replaying old test recordings. Starting RECORDING based on the most recent commit. Click here to see the affected tests
View the replaying VCR build log Step 2: Recording Mode
Caution Issues requiring attention before PR completion 🔴 Initial Recording Failed: Some tests failed during the recording step. See the table above for details. Please address these issues to complete your PR. If you believe these detections are incorrect or unrelated to your change, please raise the concern with your reviewer. View the recording VCR build log or the debug logs folder for detailed results. @GitOleksandrBokov VCR tests complete for ba79e1e! |
Part of the ongoing migration of handwritten compute files from the Apiary client library to direct HTTP calls (
transport_tpg.SendRequest). Same pattern as #18444 and the merged data source migrations #17090 / #17117.NewClient(...).GlobalAddresses.Get(project, name).Do()with aGETtoprojects/{project}/global/addresses/{name}.prefixLengthis a plain JSON number and is converted explicitly; when the field is absent (addresses without a prefix) the attribute stays0, matching the previous client's zero value.alt/prettyPrint, and the URL path is unchanged.Release Note Template for Downstream PRs (will be copied)
See Write release notes for guidance.