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

Adding ConfigContext to DeviceType #2706

New Issue
Closed
opened 2025-12-29 18:21:12 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:21:12 +01:00
Owner
Copy Link

Originally created by @sconwayubb on GitHub (Jun 28, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.6.1

Proposed Functionality

Please add ConfigContext to DeviceType that would appear in the nested Device.config_context.

Use Case

Often there are certain models of equipment that have certain attributes that apply to all devices of that model but not necessarily to all of that Platform/Role. Adding ConfigContext will allow that information to be accessible when querying for a list of Devices without additional API calls to get Custom Field data for each type.

Database Changes

class ConfigContext(models.Model):
...
    device_types = models.ManyToManyField(
        to='dcim.DeviceType',
        related_name='+',
        blank=True
    )

External Dependencies

None.

Originally created by @sconwayubb on GitHub (Jun 28, 2019). ### Environment * Python version: 3.5.2 * NetBox version: 2.6.1 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Please add ConfigContext to DeviceType that would appear in the nested Device.config_context. ### Use Case Often there are certain models of equipment that have certain attributes that apply to all devices of that model but not necessarily to all of that Platform/Role. Adding ConfigContext will allow that information to be accessible when querying for a list of Devices without additional API calls to get Custom Field data for each type. ### Database Changes ``` class ConfigContext(models.Model): ... device_types = models.ManyToManyField( to='dcim.DeviceType', related_name='+', blank=True ) ``` ### External Dependencies None.
adam closed this issue 2025-12-29 18:21:12 +01:00
adam commented 2025-12-29 18:21:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 28, 2019):

Device types define physical hardware. Config context data has no relevance to them.

@jeremystretch commented on GitHub (Jun 28, 2019): Device types define physical hardware. Config context data has no relevance to them.
adam commented 2025-12-29 18:21:13 +01:00
Author
Owner
Copy Link

@sconwayubb commented on GitHub (Jun 28, 2019):

If that's the case, then can Custom Fields be exposed on the Device list API?

@sconwayubb commented on GitHub (Jun 28, 2019): If that's the case, then can Custom Fields be exposed on the Device list API?
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
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#2706
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?