Move IP Range and FQDN in IPAM menu about nautobot-app-firewall-models HOT 4 CLOSED

I like that IF the models get pulled into core. I think if a model comes from a plugin it should stay colocated to the plugin. I support either way, we could move the two models to core and align plugin release with a minor release of Nautobot.

from nautobot-app-firewall-models.

It's an interesting question that we should clarify internally

I'm of the opinion that a user shouldn't have to know if a feature is coming from a plugin or not, that's too much complexity to expose to the end users.
As such I think it's best to have the menu organized per theme Device / Routing / Security / Ipam etc ... and a plugin should insert its menu items where ever it make the most sense.

Would love to hear more feedback on this one ? @jedelman8 @itdependsnetworks @mzbroch @chadell

from nautobot-app-firewall-models.

Only argument for keeping in the plugin nac menu i have is as of now they aren't full featured ipam objects and to me may confuse a user where it's coming from.

Maybe denote with a submenu of the plugin it's coming from as a compromise?

Just thinking from a consumer nondev perspective, find screenshots of additional models in ipam but not having that plugin installed.

from nautobot-app-firewall-models.

Marking as won't do to avoid confusion. Recommend to revisit IF iprange is pulled into core

from nautobot-app-firewall-models.