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

Filter devices for 'Has Local Context Data' #2483

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

Originally created by @bdlamprecht on GitHub (Mar 25, 2019).

Environment

  • Python version: 3.6.5
  • NetBox version: 2.5.8

Proposed Functionality

Currently, you can filter devices by things such as Has Primary IP or Has Power Ports, however, it is very difficult to find devices which have a value for Local Context Data.

Use Case

In a scenario where you have configurations being generated off of the Global config context and then potentially being replaced by data in Local config context, it would be helpful to see how many devices (and more importantly which ones) have Local contexts defined in order to see which are "snowflakes" (or different) from the rest of the devices.

This would enable you to better have an overall view of those devices which are unique and must be handled with extra care when interacting with them.

Database Changes

Unknown

External Dependencies

None

Originally created by @bdlamprecht on GitHub (Mar 25, 2019). ## Environment * Python version: 3.6.5 * NetBox version: 2.5.8 ### Proposed Functionality Currently, you can filter devices by things such as `Has Primary IP` or `Has Power Ports`, however, it is very difficult to find devices which have a value for `Local Context Data`. ### Use Case In a scenario where you have configurations being generated off of the `Global` config context and then **_potentially_** being replaced by data in `Local` config context, it would be helpful to see how many devices (and more importantly **which** ones) have `Local` contexts defined in order to see which are "snowflakes" (or different) from the rest of the devices. This would enable you to better have an overall view of those devices which are unique and must be handled with extra care when interacting with them. ### Database Changes Unknown ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:19:15 +01:00
adam closed this issue 2025-12-29 18:19:15 +01:00
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 status: accepted 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#2483
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?