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

Prefix config context #4575

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

Originally created by @Lombra on GitHub (Feb 17, 2021).

Environment

  • Python version: 3.9.1
  • NetBox version: 2.10.3

Proposed Functionality

Defining configuration context per prefix, inherited by devices which have an address in the prefix.

Use Case

Allows for defining configuration commonly shared within subnets, such as default gateway and DNS servers.

Database Changes

Adds config context field to prefix?

External Dependencies

N/A

Originally created by @Lombra on GitHub (Feb 17, 2021). ### Environment * Python version: 3.9.1 * NetBox version: 2.10.3 ### Proposed Functionality Defining configuration context per prefix, inherited by devices which have an address in the prefix. ### Use Case Allows for defining configuration commonly shared within subnets, such as default gateway and DNS servers. ### Database Changes Adds config context field to prefix? ### External Dependencies N/A
adam added the type: feature label 2025-12-29 18:37:50 +01:00
adam closed this issue 2025-12-29 18:37:50 +01:00
adam commented 2025-12-29 18:37:50 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 18, 2021):

This is easily accomplished with custom fields, is there any reason why config contexts are needed?

@DanSheps commented on GitHub (Feb 18, 2021): This is easily accomplished with custom fields, is there any reason why config contexts are needed?
adam commented 2025-12-29 18:37:51 +01:00
Author
Owner
Copy Link

@Lombra commented on GitHub (Feb 18, 2021):

I'm confused. Couldn't the same be said of any of the models that currently support config contexts?

Configuration is what I want to provide, so config context seemed like the appropriate field. As well, of course, it would work with hierarchical rendering.

@Lombra commented on GitHub (Feb 18, 2021): I'm confused. Couldn't the same be said of any of the models that currently support config contexts? Configuration is what I want to provide, so config context seemed like the appropriate field. As well, of course, it would work with hierarchical rendering.
adam commented 2025-12-29 18:37:51 +01:00
Author
Owner
Copy Link

@Lombra commented on GitHub (Feb 21, 2021):

I see now that I imagined the relationship in the opposite direction. The prefix would be a property of the config context, rather than the other way around? I don't think it affects my request, however.

@Lombra commented on GitHub (Feb 21, 2021): I see now that I imagined the relationship in the opposite direction. The prefix would be a property of the config context, rather than the other way around? I don't think it affects my request, however.
adam commented 2025-12-29 18:37:51 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 13, 2021):

Defining configuration context per prefix, inherited by devices which have an address in the prefix.

This isn't really practical to implement. You're going to be much better off employing tags. If you'd like to discuss potential solutions further, please consider opening a discussion detailing exactly what you'd like to accomplish.

@jeremystretch commented on GitHub (Apr 13, 2021): > Defining configuration context per prefix, inherited by devices which have an address in the prefix. This isn't really practical to implement. You're going to be much better off employing tags. If you'd like to discuss potential solutions further, please consider opening a [discussion](https://github.com/netbox-community/netbox/discussions/new) detailing exactly what you'd like to accomplish.
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#4575
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?