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

Add tenancy to Provider #6029

New Issue
Closed
opened 2025-12-29 19:35:52 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:35:52 +01:00
Owner
Copy Link

Originally created by @polski-g on GitHub (Jan 31, 2022).

NetBox version

v3.1.6

Feature type

Data model extension

Proposed functionality

A new field in the Provider creation/edit pages which allows user to assign a Tenant for the Provider.
A new field in the Provider detail and list pages which lists an assigned Tenant for the Provider.

Use case

Imagine company Foobar Corp has divisions Bar and Foo. Bar and Foo might each have a separate contract with a Provider. Therefore they would each have a separate Account Number to give the support personnel at Provider if there is an outage. As of now, Netbox only allows a single Account Number field for a given Provider, regardless of how many contracts your overall Foobar Corp has.

Database changes

No response

External dependencies

No response

Originally created by @polski-g on GitHub (Jan 31, 2022). ### NetBox version v3.1.6 ### Feature type Data model extension ### Proposed functionality A new field in the Provider creation/edit pages which allows user to assign a Tenant for the Provider. A new field in the Provider detail and list pages which lists an assigned Tenant for the Provider. ### Use case Imagine company **Foobar Corp** has divisions **Bar** and **Foo**. **Bar** and **Foo** might each have a _separate contract_ with a Provider. Therefore they would each have a separate Account Number to give the support personnel at Provider if there is an outage. As of now, Netbox only allows a single Account Number field for a given Provider, regardless of how many contracts your overall **Foobar Corp** has. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:35:52 +01:00
adam closed this issue 2025-12-29 19:35:52 +01:00
adam commented 2025-12-29 19:35:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 3, 2022):

Imagine company Foobar Corp has divisions Bar and Foo. Bar and Foo might each have a separate contract with a Provider.

But there's still only one provider, irrespective of its relationship with the tenants. I assume your intent here is to duplicate the provider, with each instance assigned a different tenant, but I don't think that makes sense.

As an infrastructure tool, NetBox probably isn't the best place to store contract information. If you really need to, you could add a custom field on the tenant model to track this information.

@jeremystretch commented on GitHub (Feb 3, 2022): > Imagine company Foobar Corp has divisions Bar and Foo. Bar and Foo might each have a separate contract with a Provider. But there's still only one provider, irrespective of its relationship with the tenants. I assume your intent here is to duplicate the provider, with each instance assigned a different tenant, but I don't think that makes sense. As an infrastructure tool, NetBox probably isn't the best place to store contract information. If you really need to, you could add a custom field on the tenant model to track this information.
adam commented 2025-12-29 19:35:52 +01:00
Author
Owner
Copy Link

@polski-g commented on GitHub (Feb 3, 2022):

But there's still only one provider

I agree, which is weird as to why NetBox is asking for Account Number in the Provider page; the Account Number would be unique per contract that the Provider signed with a company (its a number that the Provider created and assigned to you)

@polski-g commented on GitHub (Feb 3, 2022): > But there's still only one provider I agree, which is weird as to why NetBox is asking for Account Number in the Provider page; the Account Number would be unique per contract that the Provider signed with a company (its a number that the Provider created and assigned to you)
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 3, 2022):

The account field is provided for convenience, as most organizations only have one account per provider. If you need to manage separate contracts, that should be done outside of NetBox. It wouldn't make sense to create multiple instances of the same provider.

@jeremystretch commented on GitHub (Feb 3, 2022): The account field is provided for convenience, as most organizations only have one account per provider. If you need to manage separate contracts, that should be done outside of NetBox. It wouldn't make sense to create multiple instances of the same provider.
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@darkpixel commented on GitHub (Feb 4, 2022):

We have hundreds of accounts numbers with Comcast. It depends on the circuit, what region it's in, if it's part of their "hierarchy account" structure, etc...

@darkpixel commented on GitHub (Feb 4, 2022): We have hundreds of accounts numbers with Comcast. It depends on the circuit, what region it's in, if it's part of their "hierarchy account" structure, etc...
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 4, 2022):

I think what you need is an "provider account" model, which I don't see adding to core but could be trivial to add as a plugin. You would use this model to tie both provider and circuits together.

@DanSheps commented on GitHub (Feb 4, 2022): I think what you need is an "provider account" model, which I don't see adding to core but could be trivial to add as a plugin. You would use this model to tie both provider and circuits together.
adam commented 2025-12-29 19:35:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 6, 2022):

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.

@github-actions[bot] commented on GitHub (Apr 6, 2022): 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).
adam commented 2025-12-29 19:35:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 8, 2022):

I'm going to close this in favor of #9047, which proposes a new Account model that can be used for this purpose.

@jeremystretch commented on GitHub (Apr 8, 2022): I'm going to close this in favor of #9047, which proposes a new Account model that can be used for this purpose.
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 pending closure 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#6029
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?