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

REST API: config contexts usage for objects #11080

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

Originally created by @janhlavin on GitHub (Apr 25, 2025).

NetBox version

v4.1.11

Feature type

Other

Proposed functionality

REST API endpoint that will return the affected objects

Use case

We have a Webhook that responds to changes for Device, as part of the processing we transfer values ​​from "Config context" to surrounding systems (e.g. depending on the device type /condition for "Config context"/ we set different values ​​for "importance").

When changing the data value in "Config context" we do not know which device the change concerns.

This would involve obtaining a list, as seen in the "Config context" tab for Device:

Image

I could then get the device using:

/api/dcim/devices/?config_context_id=1

Database changes

no

External dependencies

No response

Originally created by @janhlavin on GitHub (Apr 25, 2025). ### NetBox version v4.1.11 ### Feature type Other ### Proposed functionality REST API endpoint that will return the affected objects ### Use case We have a Webhook that responds to changes for Device, as part of the processing we transfer values ​​from "Config context" to surrounding systems (e.g. depending on the device type /condition for "Config context"/ we set different values ​​for "importance"). When changing the data value in "Config context" we do not know which device the change concerns. This would involve obtaining a list, as seen in the "Config context" tab for Device: <img width="232" alt="Image" src="https://github.com/user-attachments/assets/5694820a-61e5-415a-9233-bca23c4abaa9" /> I could then get the device using: > /api/dcim/devices/?config_context_id=1 ### Database changes no ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 21:40:00 +01:00
adam closed this issue 2025-12-29 21:40:00 +01:00
adam commented 2025-12-29 21:40:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 25, 2025):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Apr 25, 2025): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:40:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 6, 2025):

This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.

@github-actions[bot] commented on GitHub (May 6, 2025): This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically.
adam commented 2025-12-29 21:40:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 13, 2025):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (May 13, 2025): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 pending closure 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#11080
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?