github-starred/pangolin
2
0
Fork 0
mirror of https://github.com/fosrl/pangolin.git synced 2026-05-08 05:39:49 -05:00
Code Issues 564 Packages Projects Releases 72 Wiki Activity

[GH-ISSUE #1259] Reuse IP based rules / Resource Rules Configuration #8595

New Issue
Closed
opened 2026-04-30 04:35:09 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-30 04:35:09 -05:00
Owner
Copy Link

Originally created by @ankycooper on GitHub (Aug 12, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1259

Originally assigned to: @Pallavikumarimdb on GitHub.

Im running v1.7.3 as a docker container trying to migrate all my resources from nginx proxy manager

What Im struggling with there is not way to define ip whitelisting policies once / centrally and use them across a common set of resources rather than defining them from scratch for every resource.

would like the following features if possible:

  • Address aliases
  • resource specific rules and global inherited rules
  • reuse of rules
  • ability clone resource and change the dns name and targets
Originally created by @ankycooper on GitHub (Aug 12, 2025). Original GitHub issue: https://github.com/fosrl/pangolin/issues/1259 Originally assigned to: @Pallavikumarimdb on GitHub. Im running v1.7.3 as a docker container trying to migrate all my resources from nginx proxy manager What Im struggling with there is not way to define ip whitelisting policies once / centrally and use them across a common set of resources rather than defining them from scratch for every resource. would like the following features if possible: - Address aliases - resource specific rules and global inherited rules - reuse of rules - ability clone resource and change the dns name and targets
GiteaMirror added the enhancement label 2026-04-30 04:35:09 -05:00
GiteaMirror commented 2026-04-30 04:35:11 -05:00
Author
Owner
Copy Link

@Pallavikumarimdb commented on GitHub (Aug 12, 2025):

Hi @ankycooper , Thanks for raising this request - the need to centrally manage and reuse IP-based rules across multiple resources is definitely valid.

This request overlaps with features already in progress:

  • PR #1248 : adds reusable IP sets (address aliases) that can be applied across resources.
  • PR #1231 : introduces rule templates, allowing reuse of rules and a global + resource-specific model (close to inheritance).

Cloning resources and a full override-based inheritance model aren’t covered yet and would need to be added separately.

<!-- gh-comment-id:3177904388 --> @Pallavikumarimdb commented on GitHub (Aug 12, 2025): Hi @ankycooper , Thanks for raising this request - the need to centrally manage and reuse IP-based rules across multiple resources is definitely valid. This request overlaps with features already in progress: * **PR #1248** : adds reusable IP sets (address aliases) that can be applied across resources. * **PR #1231** : introduces rule templates, allowing reuse of rules and a global + resource-specific model (close to inheritance). Cloning resources and a full override-based inheritance model aren’t covered yet and would need to be added separately.
GiteaMirror commented 2026-04-30 04:35:11 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 27, 2025):

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

<!-- gh-comment-id:3226251772 --> @github-actions[bot] commented on GitHub (Aug 27, 2025): This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
GiteaMirror commented 2026-04-30 04:35:11 -05:00
Author
Owner
Copy Link

@miloschwartz commented on GitHub (Sep 27, 2025):

Thanks this is actively getting worked on. Converting this to a discussion since it's a feature request for people to upvote.

<!-- gh-comment-id:3342113273 --> @miloschwartz commented on GitHub (Sep 27, 2025): Thanks this is actively getting worked on. Converting this to a discussion since it's a feature request for people to upvote.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
authentication
bug
config
dependencies
docker
documentation
enhancement
good first issue
help wanted
Improvement
Look Into
needs investigating
networking
new feature
non-critical bug
potential bug
pull-request
Mirrored from GitHub Pull Request
 question
reverse proxy
Security
stale
ui
wontfix
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/pangolin#8595
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?