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

Local Config Context on Tenant #5363

New Issue
Closed
opened 2025-12-29 19:27:09 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:27:09 +01:00
Owner
Copy Link

Originally created by @ziggekatten on GitHub (Sep 14, 2021).

NetBox version

v3.0.2

Feature type

New functionality

Proposed functionality

Just as individual objects have their local context specific for the object, there are from an automation perspective cases where parameters are needed related to Tenants.

Use case

An example, different Tenants have different asset management systems that automation code should talk to. Fetching this from Config Context on an Tenant instead of clogging down the Global Config Contexts with a lot of Tenant specific things would be beneficial.

Another is Tenant specific security and monitoring parameters, that from an automation perspective would be great to have in a Config Context

Database changes

Probably the architecture for Config Context could be reused on the Tenant object

External dependencies

No response

Originally created by @ziggekatten on GitHub (Sep 14, 2021). ### NetBox version v3.0.2 ### Feature type New functionality ### Proposed functionality Just as individual objects have their local context specific for the object, there are from an automation perspective cases where parameters are needed related to Tenants. ### Use case An example, different Tenants have different asset management systems that automation code should talk to. Fetching this from Config Context on an Tenant instead of clogging down the Global Config Contexts with a lot of Tenant specific things would be beneficial. Another is Tenant specific security and monitoring parameters, that from an automation perspective would be great to have in a Config Context ### Database changes Probably the architecture for Config Context could be reused on the Tenant object ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:27:09 +01:00
adam closed this issue 2025-12-29 19:27:09 +01:00
adam commented 2025-12-29 19:27:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 14, 2021):

Config context only applies to devices and virtual machines. It sounds like what you want is custom fields, which is already supported.

@jeremystretch commented on GitHub (Sep 14, 2021): Config context only applies to devices and virtual machines. It sounds like what you want is custom fields, which is already supported.
adam commented 2025-12-29 19:27:10 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Sep 15, 2021):

Of course my first aproach was custom fields. However, when needing a list of items, which in a custom field would be of type selection, these cant be unique for a tenant.

One solution would be a custom field if type JSON was available.

@ziggekatten commented on GitHub (Sep 15, 2021): Of course my first aproach was custom fields. However, when needing a list of items, which in a custom field would be of type selection, these cant be unique for a tenant. One solution would be a custom field if type JSON was available.
adam commented 2025-12-29 19:27:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 16, 2021):

One solution would be a custom field if type JSON was available.

Sounds like that could be a solid feature request. However, I don't think it makes sense to extend configuration contexts to the Tenant model.

@jeremystretch commented on GitHub (Sep 16, 2021): > One solution would be a custom field if type JSON was available. Sounds like that could be a solid feature request. However, I don't think it makes sense to extend configuration contexts to the Tenant model.
adam commented 2025-12-29 19:27:10 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Sep 16, 2021):

A JSON type custom field would solve the usecases we struggle with. If that seems like a reasonable festure request, I open a new one for that and we close this one.

@ziggekatten commented on GitHub (Sep 16, 2021): A JSON type custom field would solve the usecases we struggle with. If that seems like a reasonable festure request, I open a new one for that and we close this one.
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 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#5363
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?