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

Transactional APIs #6293

New Issue
Closed
opened 2025-12-29 19:39:03 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:39:03 +01:00
Owner
Copy Link

Originally created by @jeremyrambo on GitHub (Apr 4, 2022).

NetBox version

v3.1.9

Feature type

New functionality

Proposed functionality

I would like the ability to BEGIN a transaction (think DB transaction) before I may a series of API calls. Then when I am done with one more API calls I would like to COMMIT that transaction or ROLLBACK the transaction depending on the response from each request.

The BEGIN would return a unique transaction ID I would retain; I would then use this ID to commit or rollback the API calls I made.

Use case

It allows uses to make a series of API calls as if they are occurring under a single call that can be reverted.

Database changes

No response

External dependencies

No response

Originally created by @jeremyrambo on GitHub (Apr 4, 2022). ### NetBox version v3.1.9 ### Feature type New functionality ### Proposed functionality I would like the ability to BEGIN a transaction (think DB transaction) before I may a series of API calls. Then when I am done with one more API calls I would like to COMMIT that transaction or ROLLBACK the transaction depending on the response from each request. The BEGIN would return a unique transaction ID I would retain; I would then use this ID to commit or rollback the API calls I made. ### Use case It allows uses to make a series of API calls as if they are occurring under a single call that can be reverted. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:39:03 +01:00
adam closed this issue 2025-12-29 19:39:03 +01:00
adam commented 2025-12-29 19:39:03 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 5, 2022):

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 5, 2022): 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 19:39:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 22, 2022):

Closing as there has been no further reply from OP. If this is something you'd still like to pursue, I invite you to start a discussion to engage with other community members and discuss potential avenues toward implementation. Once sufficient detail has been gathered, you are welcome to request that this FR be re-opened, or open a new FR.

@jeremystretch commented on GitHub (Apr 22, 2022): Closing as there has been no further reply from OP. If this is something you'd still like to pursue, I invite you to start a [discussion](https://github.com/netbox-community/netbox/discussions/new) to engage with other community members and discuss potential avenues toward implementation. Once sufficient detail has been gathered, you are welcome to request that this FR be re-opened, or open a new FR.
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: revisions needed 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#6293
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?