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

change ID is returned on API calls that modify data. #3824

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

Originally created by @baldgeek on GitHub (Jul 1, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.6

Proposed Functionality

Any patch, delete, creation returns the change ID for the change record created so that the object change API can be called to verify or collect data for rollback.

Use Case

Be able to find the change record for the work just done to pull change record for rollback or verification.

Database Changes

I do not believe this would require and database changes. These records already exist.

External Dependencies

I don't think there is any external dependencies, however timing of when the change record is created vs when the results are returned to the API call might make this problematic to implement.

Originally created by @baldgeek on GitHub (Jul 1, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.8.6 ### Proposed Functionality Any patch, delete, creation returns the change ID for the change record created so that the object change API can be called to verify or collect data for rollback. ### Use Case Be able to find the change record for the work just done to pull change record for rollback or verification. ### Database Changes I do not believe this would require and database changes. These records already exist. ### External Dependencies I don't think there is any external dependencies, however timing of when the change record is created vs when the results are returned to the API call might make this problematic to implement.
adam closed this issue 2025-12-29 18:31:22 +01:00
adam commented 2025-12-29 18:31:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 1, 2020):

It's a neat idea, but unfortunately this would require far too much development effort (and a bit of performance impact) to warrant the minor convenience. The way DRF employs serializers doesn't easily allow for the arbitrary attachment of additional information such as this. However, you can easily fetch the most recent change record for any object by querying the /api/extras/object-changes/ API endpoint.

@jeremystretch commented on GitHub (Jul 1, 2020): It's a neat idea, but unfortunately this would require far too much development effort (and a bit of performance impact) to warrant the minor convenience. The way DRF employs serializers doesn't easily allow for the arbitrary attachment of additional information such as this. However, you can easily fetch the most recent change record for any object by querying the `/api/extras/object-changes/` API endpoint.
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#3824
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?