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
@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.
@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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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:
@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:
Cloning resources and a full override-based inheritance model aren’t covered yet and would need to be added separately.
@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.
@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.