Evaluate using dynamic groups inside of `AddressObject` about nautobot-app-firewall-models HOT 3 OPEN

At this time the performance limitations with dynamic groups makes this a non-starter at scale. We should keep the issue and reevaluate pending performance improvements for dynamic groups.

Dynamic Groups start having performance degradation over the 500 groups count on a single content type.

from nautobot-app-firewall-models.

I feel like the development and added functionality this would bring to this plugin would be worth it to keep moving forward, even if there is a warning or a opt in configuration parameter to enable this. Hopefully when the feature is ready in this plugin Nautobot Core would have an update... Because I really want this feature

from nautobot-app-firewall-models.

I have some work on logical grouping which is solving this from a different PoV. I see this really relevant when it comes to controller based systems and how each group is treated as unique and how the group has access to certain items depending on where it's at within the tree. From a firewall object modeling perspective some of the patterns in dynamic groups does not solve this problem case and introduces a level of complexity in managing uniqueness.

I'm open to discussions around the topic and personally would love to swap out <type>ObjectGroup to a generic upstream group & how we can assign X content types to the same group. I am committed to keeping this issue open until we have a more elegant solution available in the plugin/core.

from nautobot-app-firewall-models.