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

Manufacturer as Config Context Assignment Field #9511

New Issue
Closed
opened 2025-12-29 20:50:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:50:49 +01:00
Owner
Copy Link

Originally created by @thibaut-probst on GitHub (Apr 22, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.6.9

Feature type

Data model extension

Proposed functionality

Have the Manufacturer field as part of the Config Context assignment fields

Use case

We would need to use it to map our config contexts to specific device roles of different manufacturers. Indeed, we have different config context applied per firewall technology and only the Manufacturer field could help properly target the right devices associated to these device roles for the given technology.

Database changes

Add the Manufacturer field in the Config Context assignment

External dependencies

No response

Originally created by @thibaut-probst on GitHub (Apr 22, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.6.9 ### Feature type Data model extension ### Proposed functionality Have the Manufacturer field as part of the Config Context assignment fields ### Use case We would need to use it to map our config contexts to specific device roles of different manufacturers. Indeed, we have different config context applied per firewall technology and only the Manufacturer field could help properly target the right devices associated to these device roles for the given technology. ### Database changes Add the Manufacturer field in the Config Context assignment ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:50:49 +01:00
adam closed this issue 2025-12-29 20:50:50 +01:00
adam commented 2025-12-29 20:50:50 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Apr 22, 2024):

Duplicate of #14508, closing.

@arthanson commented on GitHub (Apr 22, 2024): Duplicate of #14508, closing.
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#9511
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?