starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Ability to assign a Tenant to an Aggregate #3955

New Issue
Closed
opened 2025-12-29 18:32:16 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:32:16 +01:00
Owner
Copy Link

Originally created by @falz on GitHub (Aug 7, 2020).

Originally assigned to: @DanSheps on GitHub.

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

Originally created by @falz on GitHub (Aug 7, 2020). Originally assigned to: @DanSheps on GitHub. There is no current way to assign an Aggregate (/ipam/aggregates/) to a tenant in Netbox. ### Environment * Python version: * NetBox version: 2.8.0 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### 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. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### 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_/ <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam added the status: acceptedtype: feature labels 2025-12-29 18:32:16 +01:00
adam closed this issue 2025-12-29 18:32:16 +01:00
adam commented 2025-12-29 18:32:17 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 24, 2020):

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.

@stale[bot] commented on GitHub (Sep 24, 2020): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3955
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?