Add the "Tenant" field to the "Address Object" model.

[ghmn256]

Environment

• Nautobot version: 1.5.23
• nautobot-plugin-firewall-model version: 1.2.1

Proposed Functionality

Add the "Tenant" field to the "Address Object" model.

Use Case

For our organization, we consider several types of adress objects to be owned by teams in our organization. For instance, an fqdn typically belongs to a specific host (maybe via DHCP), which in turn is owned by a team in our organization. Same goes for subnet (prefix in nautobot terms), as well as ip ranges.

For instance, we have a specific subnet for linux hosts and we want the firewall policies for that subnet to be managed by the linux team. Having the tenant as a field in the address object would let us use that information for authorization in the rest of our automated workflow. Another example would be for being able to inform tenants that a new firewall policy has been created, and that that policy involves an address object that belongs to them

I think if both ip addresses and prefixes can have a tenant field in core nautobot, there's no reason to keep that information away from adress objects.

2 other options:

• You could add the tenant to FQDN and ip ranges as well as address objects,
• You could add the tenant only to FQDN and ip ranges, and have the address object inherit the tenant based on the object it's referring to. (this would make it so the tenant of the address object is always the same as the tenant of the underlying object, which is probably a good idea)