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

Deep merge for Config Context Data Set via API #2491

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

Originally created by @dnyt84 on GitHub (Apr 3, 2019).

Environment

  • Python version: 3.6.3
  • NetBox version: 2.5.8

Proposed Functionality
Currently when doing an API Patch to /extras/config-contexts/{id}/ it overwrites all existing Data stored.

Use Case
A Deep merge feature would make smaller changes easier as I would not necessary need to know what else is stored in the Data set.

I would imagine this could be done via a new API endpoint
/extras/config-contexts-merge/{id}/
or possibly via a flag that would allow a deep merge or overwrite.

We would not want to loose the option to complacently overwrite the current Data Set.
Database Changes
None
External Dependencies
None

Originally created by @dnyt84 on GitHub (Apr 3, 2019). **Environment** * Python version: 3.6.3 * NetBox version: 2.5.8 **Proposed Functionality** Currently when doing an API Patch to /extras/config-contexts/{id}/ it overwrites all existing Data stored. **Use Case** A Deep merge feature would make smaller changes easier as I would not necessary need to know what else is stored in the Data set. I would imagine this could be done via a new API endpoint /extras/config-contexts-merge/{id}/ or possibly via a flag that would allow a deep merge or overwrite. We would not want to loose the option to complacently overwrite the current Data Set. **Database Changes** None **External Dependencies** None
adam closed this issue 2025-12-29 18:19:19 +01:00
adam commented 2025-12-29 18:19:20 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2019):

This would deviate from the expected behavior of the REST API, which is standard across all objects. You'll need to retrieve the data first and then update accordingly.

@jeremystretch commented on GitHub (Apr 4, 2019): This would deviate from the expected behavior of the REST API, which is standard across all objects. You'll need to retrieve the data first and then update accordingly.
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
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#2491
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?