-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Subnet IP Collection Patch Support #17425
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
SirGitsalot
merged 4 commits into
GoogleCloudPlatform:main
from
dhruv-23101998:dhruvagarwal/subnet-ip-collection-patch-support
May 6, 2026
+184
−1
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking at the config here and the debug log from the test, this update step isn't actually testing an update of the
ip_collectionfield, since the value didn't change between steps. That is, in the create step it wasprojects/ci-test-project-188019/regions/us-central1/subnetworks/tf-test-sub-jx0ch37msg, and in the update step it was stillprojects/ci-test-project-188019/regions/us-central1/subnetworks/tf-test-sub-jx0ch37msg. To trigger an update of the field, you'll need to create a newgoogle_compute_public_delegated_prefixand reference it here.An update of the subnetwork is happening at this point in the test, but it's because the values of
stack_typeandipv6_access_typechanged.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please elaborate a little more? In the previous configuration, the subnetwork doesn't have the IP collection. Here we added IP Collection and it seems to be correctly updated.
projects/ci-test-project-188019/regions/us-central1/subnetworks/tf-test-sub-jx0ch37msgis the subnetwork reference and not IP collection reference. Also, in this update test case, we want to test whether the Subnetwork is correctly associated with IP collection or not. As such IP collection itself won't get any update.Are you asking to create the
google_compute_public_delegated_prefixin the update step instead of the create step? If yes, how does this matter, as we only want to test the update in the subnetwork.Also, just for context, the subnetwork cannot be updated just with the IP collection.
ip_collection,stack_typeandipv6_access_typehas to be updated together. In previous configuration, IP collection was absent which we added in the next update configuration along with differentstack_typeandipv6_access_type.If I'm misunderstanding something, please feel free to let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I was looking at the wrong request/response pair in the log. LGTM