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

Manufacturer-based Config Context Assignment #10388

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

Originally created by @paulcarre07 on GitHub (Oct 21, 2024).

NetBox version

v4.1.4

Feature type

Data model extension

Triage priority

This is a very minor change

Proposed functionality

I propose adding the ability to assign a config context directly to a manufacturer. Currently, it's not possible to apply a config context across all devices from a given manufacturer.

This enhancement could involve updates to the config context assignment workflows and may require adjustments to the data model to support manufacturer-level scoping in addition to device type and role scoping. Ideally, the user interface would provide a new option under config contexts where manufacturers could be selected alongside the existing device role and type options

Use case

This feature would be particularly helpful for users who manage large-scale deployments where many devices from the same manufacturer share the same configuration. Instead of manually applying a config context to each device type or role, users could apply it once at the manufacturer level, ensuring consistency across all devices from that manufacturer. This would simplify the configuration process, reduce human error, and save time in maintaining and updating configurations, especially in environments with multiple devices from the same vendor

Database changes

No response

External dependencies

No response

Originally created by @paulcarre07 on GitHub (Oct 21, 2024). ### NetBox version v4.1.4 ### Feature type Data model extension ### Triage priority This is a very minor change ### Proposed functionality I propose adding the ability to assign a config context directly to a manufacturer. Currently, it's not possible to apply a config context across all devices from a given manufacturer. This enhancement could involve updates to the config context assignment workflows and may require adjustments to the data model to support manufacturer-level scoping in addition to device type and role scoping. Ideally, the user interface would provide a new option under config contexts where manufacturers could be selected alongside the existing device role and type options ### Use case This feature would be particularly helpful for users who manage large-scale deployments where many devices from the same manufacturer share the same configuration. Instead of manually applying a config context to each device type or role, users could apply it once at the manufacturer level, ensuring consistency across all devices from that manufacturer. This would simplify the configuration process, reduce human error, and save time in maintaining and updating configurations, especially in environments with multiple devices from the same vendor ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicatenetbox labels 2025-12-29 21:30:47 +01:00
adam closed this issue 2025-12-29 21:30:47 +01:00
adam commented 2025-12-29 21:30:48 +01:00
Author
Owner
Copy Link

@chris240189 commented on GitHub (Oct 21, 2024):

I use the platform specific config context for that.
That is how all my arista EOS switches get some defaults.

@chris240189 commented on GitHub (Oct 21, 2024): I use the platform specific config context for that. That is how all my arista EOS switches get some defaults.
adam commented 2025-12-29 21:30:48 +01:00
Author
Owner
Copy Link

@pl0xym0r commented on GitHub (Oct 22, 2024):

Workaround could be tags:
Create tag for manufacturer
Create cc and assign tag
Assign tag to your device

Device will inherit the cc

@pl0xym0r commented on GitHub (Oct 22, 2024): Workaround could be tags: Create tag for manufacturer Create cc and assign tag Assign tag to your device Device will inherit the cc
adam commented 2025-12-29 21:30:48 +01:00
Author
Owner
Copy Link

@paulcarre07 commented on GitHub (Oct 22, 2024):

Workaround could be tags: Create tag for manufacturer Create cc and assign tag Assign tag to your device

Device will inherit the cc

Thank you for the suggestion! I'll go ahead and implement the workaround with tags for now.

@paulcarre07 commented on GitHub (Oct 22, 2024): > Workaround could be tags: Create tag for manufacturer Create cc and assign tag Assign tag to your device > > Device will inherit the cc Thank you for the suggestion! I'll go ahead and implement the workaround with tags for now.
adam commented 2025-12-29 21:30:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 22, 2024):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14508 for further discussion.

@jeremystretch commented on GitHub (Oct 22, 2024): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #14508 for further discussion.
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 netbox status: duplicate 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#10388
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?