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

Revision #592

New Issue
Closed
opened 2025-12-29 16:23:38 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:23:38 +01:00
Owner
Copy Link

Originally created by @john-arvid on GitHub (Dec 30, 2016).

May be a duplicate of #683

Would like brainstorming around revision and how this could be solved today or with a new enhancement.

I have several users that are human, and they as I will make mistakes. I need a way to revert changes done to "anything" so that when another user or me finds an faulty registration, we could change back and do the proper update.

Is this something I could implement in the existing version? (in postgres, django, a routine or php?)

Originally created by @john-arvid on GitHub (Dec 30, 2016). May be a duplicate of #683 Would like brainstorming around revision and how this could be solved today or with a new enhancement. I have several users that are human, and they as I will make mistakes. I need a way to revert changes done to "anything" so that when another user or me finds an faulty registration, we could change back and do the proper update. Is this something I could implement in the existing version? (in postgres, django, a routine or php?)
adam closed this issue 2025-12-29 16:23:39 +01:00
adam commented 2025-12-29 16:23:39 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Dec 30, 2016):

This feature could be implemented using
https://github.com/etianen/django-reversion

I used it in the past and it is flexible enough to achieve very powerful
results.

On Fri, Dec 30, 2016, 14:47 john-arvid, notifications@github.com wrote:

May be a duplicate of #683
https://github.com/digitalocean/netbox/issues/683

Would like brainstorming around revision and how this could be solved
today or with a new enhancement.

I have several users that are human, and they as I will make mistakes. I
need a way to revert changes done to "anything" so that when another user
or me finds an faulty registration, we could change back and do the proper
update.

Is this something I could implement in the existing version? (in postgres,
django, a routine or php?)

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digitalocean/netbox/issues/758, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABfg5ioV7PXMM_4iM1c047D8LHq5NHmSks5rNV_DgaJpZM4LYW9r
.

@jsenecal commented on GitHub (Dec 30, 2016): This feature could be implemented using https://github.com/etianen/django-reversion I used it in the past and it is flexible enough to achieve very powerful results. On Fri, Dec 30, 2016, 14:47 john-arvid, <notifications@github.com> wrote: > May be a duplicate of #683 > <https://github.com/digitalocean/netbox/issues/683> > > Would like brainstorming around revision and how this could be solved > today or with a new enhancement. > > I have several users that are human, and they as I will make mistakes. I > need a way to revert changes done to "anything" so that when another user > or me finds an faulty registration, we could change back and do the proper > update. > > Is this something I could implement in the existing version? (in postgres, > django, a routine or php?) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/digitalocean/netbox/issues/758>, or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABfg5ioV7PXMM_4iM1c047D8LHq5NHmSks5rNV_DgaJpZM4LYW9r> > . >
adam commented 2025-12-29 16:23:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 3, 2017):

I looked into the possibility of using django-reversion early on in the development of NetBox. Unfortunately, it's not well-suited for a data model so complex as what we have.

For example, suppose a user deletes a device, and then some time later wants to restore it. We'd need to validate not on the device object, but all of its related connections, addresses, rack space, etc. and have a plan to elegantly handle every potential conflict. It'd be an amazing feature, for sure, but it's not something that we can dedicate effort to in the near future.

@jeremystretch commented on GitHub (Jan 3, 2017): I looked into the possibility of using django-reversion early on in the development of NetBox. Unfortunately, it's not well-suited for a data model so complex as what we have. For example, suppose a user deletes a device, and then some time later wants to restore it. We'd need to validate not on the device object, but all of its related connections, addresses, rack space, etc. _and_ have a plan to elegantly handle every potential conflict. It'd be an amazing feature, for sure, but it's not something that we can dedicate effort to in the near future.
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#592
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?