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

Setting data_file id over the REST Api #9171

New Issue
Closed
opened 2025-12-29 20:46:30 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:46:30 +01:00
Owner
Copy Link

Originally created by @maxiestudies on GitHub (Jan 30, 2024).

NetBox version

v3.6.9

Feature type

Change to existing functionality

Proposed functionality

Make it possible to set the config-context's data_file id on POST, PUT and/or PATCH requests. At the moment only the data_source can be set as a string, but the data_file is returned on the response.

Use case

I keep the config contexts on a git repository and wrote tooling to create new config contexts in Netbox whenever a new file is commited to the main branch. I would like to also set the data_file id in the request so that no further operation is needed for the config context to be matched to the file.

Database changes

No response

External dependencies

No response

Originally created by @maxiestudies on GitHub (Jan 30, 2024). ### NetBox version v3.6.9 ### Feature type Change to existing functionality ### Proposed functionality Make it possible to set the config-context's data_file id on POST, PUT and/or PATCH requests. At the moment only the data_source can be set as a string, but the data_file is returned on the response. ### Use case I keep the config contexts on a git repository and wrote tooling to create new config contexts in Netbox whenever a new file is commited to the main branch. I would like to also set the data_file id in the request so that no further operation is needed for the config context to be matched to the file. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: low labels 2025-12-29 20:46:30 +01:00
adam closed this issue 2025-12-29 20:46:30 +01:00
adam commented 2025-12-29 20:46:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 21, 2024):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 21, 2024): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:46:31 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 20, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Sep 20, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 complexity: low pending closure status: needs owner 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#9171
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?