Fetch AWS VPC peering connections from both requester and accepter sides#645
Merged
RomanMelnyk113 merged 2 commits intomainfrom Feb 23, 2026
Merged
Fetch AWS VPC peering connections from both requester and accepter sides#645RomanMelnyk113 merged 2 commits intomainfrom
RomanMelnyk113 merged 2 commits intomainfrom
Conversation
samuelvl
approved these changes
Feb 23, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Previously, only peerings where the account VPC was the requester were fetched, causing peered VPCs to be missed when the account VPC was the accepter. This fix queries both
requester-vpc-info.vpc-idandaccepter-vpc-info.vpc-idfilters and reads the remote peer info from the correct side of each connection