[PR #2842] [MERGED] chore: fix autogroup:self with other acl rules #2889

Closed
opened 2025-12-29 04:19:31 +01:00 by adam · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/juanfont/headscale/pull/2842
Author: @vdovhanych
Created: 10/31/2025
Status: Merged
Merged: 11/2/2025
Merged by: @kradalby

Base: mainHead: fix-autogroup-self-policy


📝 Commits (1)

  • f69c5ce chore: fix autogroup:self with other acl rules

📊 Changes

4 files changed (+559 additions, -175 deletions)

View changed files

📝 hscontrol/policy/v2/filter.go (+220 -144)
📝 hscontrol/policy/v2/filter_test.go (+67 -0)
📝 hscontrol/policy/v2/policy_test.go (+80 -0)
📝 integration/acl_test.go (+192 -31)

📄 Description

  • have read the CONTRIBUTING.md file
  • raised a GitHub issue or discussed it on the projects chat beforehand
  • added unit tests
  • added integration tests
  • updated documentation if needed
  • updated CHANGELOG.md

I try to fix this #2838 issue and add tests that catch this issue.
Cursor AI was used for the tests and logic validation.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/juanfont/headscale/pull/2842 **Author:** [@vdovhanych](https://github.com/vdovhanych) **Created:** 10/31/2025 **Status:** ✅ Merged **Merged:** 11/2/2025 **Merged by:** [@kradalby](https://github.com/kradalby) **Base:** `main` ← **Head:** `fix-autogroup-self-policy` --- ### 📝 Commits (1) - [`f69c5ce`](https://github.com/juanfont/headscale/commit/f69c5ce8f370aa01451f7791edd83066fe6b2ef0) chore: fix autogroup:self with other acl rules ### 📊 Changes **4 files changed** (+559 additions, -175 deletions) <details> <summary>View changed files</summary> 📝 `hscontrol/policy/v2/filter.go` (+220 -144) 📝 `hscontrol/policy/v2/filter_test.go` (+67 -0) 📝 `hscontrol/policy/v2/policy_test.go` (+80 -0) 📝 `integration/acl_test.go` (+192 -31) </details> ### 📄 Description <!-- Headscale is "Open Source, acknowledged contribution", this means that any contribution will have to be discussed with the Maintainers before being submitted. This model has been chosen to reduce the risk of burnout by limiting the maintenance overhead of reviewing and validating third-party code. Headscale is open to code contributions for bug fixes without discussion. If you find mistakes in the documentation, please submit a fix to the documentation. --> <!-- Please tick if the following things apply. You… --> - [ ] have read the [CONTRIBUTING.md](./CONTRIBUTING.md) file - [ ] raised a GitHub issue or discussed it on the projects chat beforehand - [ ] added unit tests - [ ] added integration tests - [ ] updated documentation if needed - [ ] updated CHANGELOG.md <!-- If applicable, please reference the issue using `Fixes #XXX` and add tests to cover your new code. --> I try to fix this #2838 issue and add tests that catch this issue. Cursor AI was used for the tests and logic validation. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
adam added the pull-request label 2025-12-29 04:19:31 +01:00
adam closed this issue 2025-12-29 04:19:31 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#2889