Ability to assign a Tenant to an Aggregate

[falz]

There is no current way to assign an Aggregate (/ipam/aggregates/) to a tenant in Netbox.

Environment

• Python version:
• NetBox version: 2.8.0

Proposed Functionality

In a service provider context, we track aggregates as a source of truth for our customers' routes (and ours). There is no direct method to tie this Aggregate to a Tenant in Netbox, making it hard to find all resources of a tenant.

Use Case

It does look like one could add a matching prefix for this aggregate, but this does not always match our configurations.

For example, we have some customers with an aggregate /16 but are not advertising the entire thing, so we opt to not create a prefix in Netbox.

Having this additional correlation would help track all netbox objects related to a tenant at /tenancy/tenants/tenantslug/

Database Changes

External Dependencies

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.