starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

changelog does not retain object creation after it is deleted #5401

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

Originally created by @michaeldialpad on GitHub (Sep 21, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.1

Python version

3.7

Steps to Reproduce

  1. create new prefix object
  2. validated CREATE changelog entry is present
  3. delete newly created prefix object
  4. validated DELETE changelog entry is present, but CREATE changelog entry is gone

Expected Behavior

I would expect changelog to keep previous change state if it is deleted

Observed Behavior

once object is deleted, changelog is gone

Originally created by @michaeldialpad on GitHub (Sep 21, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.1 ### Python version 3.7 ### Steps to Reproduce 1. create new prefix object 2. validated CREATE changelog entry is present 3. delete newly created prefix object 4. validated DELETE changelog entry is present, but CREATE changelog entry is gone ### Expected Behavior I would expect changelog to keep previous change state if it is deleted ### Observed Behavior once object is deleted, changelog is gone
adam added the type: bugstatus: accepted labels 2025-12-29 19:27:31 +01:00
adam closed this issue 2025-12-29 19:27:31 +01:00
adam commented 2025-12-29 19:27:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 21, 2021):

Looks like this is a regression introduced in 88d2441ab3 when adding the changelog reverse relationship for GraphQL. Django forces a CASCADE action on this relationship when the related object is deleted. We can probably just omit the reverse relationship from the model and make the forward query directly within the GraphQL object.

Thanks for the report!

@jeremystretch commented on GitHub (Sep 21, 2021): Looks like this is a regression introduced in 88d2441ab377ddac17ecf59028fa07623f97f2ab when adding the `changelog` reverse relationship for GraphQL. Django forces a `CASCADE` action on this relationship when the related object is deleted. We can probably just omit the reverse relationship from the model and make the forward query directly within the GraphQL object. Thanks for the report!
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: accepted type: bug
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#5401
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?