[PR #6526] [management] When collecting group and peer IDs from policies, do so directionally #26021

Open
opened 2026-08-05 07:06:47 -04:00 by saavagebueno · 0 comments
Owner

Original Pull Request: https://github.com/netbirdio/netbird/pull/6526

State: open
Merged: No


Describe your changes

In affected peer calculation, when walking policies of groups and peers, only use opposite sides of those policies; i.e. if a policy rule sources include the group, use the rule's destinations, and vice-versa. Similarly, if a rule's SourceResource matches a peer from the change set, use rule's DesstinationResource and vice-versa.

Stack

Checklist

  • Is it a bug fix
  • Is a typo/documentation fix
  • Is a feature enhancement
  • It is a refactor
  • Created tests that fail without the change (if possible)
  • This change does not modify the public API, gRPC protocols, functionality behavior, CLI / service flags, or introduce a new feature — OR I have discussed it with the NetBird team beforehand (link the issue / Slack thread in the description). See CONTRIBUTING.md.

By submitting this pull request, you confirm that you have read and agree to the terms of the Contributor License Agreement.

Documentation

Select exactly one:

  • I added/updated documentation for this change
  • Documentation is not needed for this change (explain why)

Docs PR URL (required if "docs added" is checked)

Paste the PR link from https://github.com/netbirdio/docs here:

https://github.com/netbirdio/docs/pull/__

Summary by CodeRabbit

  • Refactor

    • Improved how policy changes are analyzed to determine the affected peer and group impact, using directionally-derived extraction from policy rules for more accurate and deterministic results.
  • Tests

    • Reworked resolver unit tests to validate precise affected peer/group sets derived from policy source/destination direction rules, including expanded coverage for mixed resource types and allowlist edge cases.
    • Updated affected-peers coverage-matrix expectations and tightened assertions to compare exact included/excluded sets.
**Original Pull Request:** https://github.com/netbirdio/netbird/pull/6526 **State:** open **Merged:** No --- ## Describe your changes In affected peer calculation, when walking policies of groups and peers, only use opposite sides of those policies; i.e. if a policy rule sources include the group, use the rule's destinations, and vice-versa. Similarly, if a rule's SourceResource matches a peer from the change set, use rule's DesstinationResource and vice-versa. ## Issue ticket number and link ## Stack <!-- branch-stack --> ### Checklist - [ ] Is it a bug fix - [ ] Is a typo/documentation fix - [x] Is a feature enhancement - [ ] It is a refactor - [ ] Created tests that fail without the change (if possible) - [x] This change does **not** modify the public API, gRPC protocols, functionality behavior, CLI / service flags, or introduce a new feature — **OR** I have discussed it with the NetBird team beforehand (link the issue / Slack thread in the description). See [CONTRIBUTING.md](https://github.com/netbirdio/netbird/blob/main/CONTRIBUTING.md#discuss-changes-with-the-netbird-team-first). > By submitting this pull request, you confirm that you have read and agree to the terms of the [Contributor License Agreement](https://github.com/netbirdio/netbird/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT.md). ## Documentation Select exactly one: - [ ] I added/updated documentation for this change - [x] Documentation is **not needed** for this change (explain why) ### Docs PR URL (required if "docs added" is checked) Paste the PR link from https://github.com/netbirdio/docs here: https://github.com/netbirdio/docs/pull/__ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Refactor** * Improved how policy changes are analyzed to determine the affected peer and group impact, using directionally-derived extraction from policy rules for more accurate and deterministic results. * **Tests** * Reworked resolver unit tests to validate precise affected peer/group sets derived from policy source/destination direction rules, including expanded coverage for mixed resource types and allowlist edge cases. * Updated affected-peers coverage-matrix expectations and tightened assertions to compare exact included/excluded sets. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
saavagebueno added the pull-request label 2026-08-05 07:06:47 -04:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#26021