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

Changelog Retention: keep last 10 entries #6481

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

Originally created by @PieterL75 on GitHub (May 16, 2022).

NetBox version

v3.2.2

Feature type

Change to existing functionality

Proposed functionality

The Changelog retention is not based on a date. All older then (your preference here) days will be removed (60 days in my case)
I now came across an issue, that happened later than 60 days ago. I needed to know who created it and made the last update.

This made me think, it might be useful to always keep the last 10 changelog items of an object, even if they are older than (60) days, and always keep the 'created' item.

Use case

Sometimes we need to see what happened to an object that had no changes in a long time. Who created it ? when was the last change and what was the change.
If we keep the last 10 items and the creation log item, then we have good forensics to analyze problems in the past

Database changes

None

External dependencies

No response

Originally created by @PieterL75 on GitHub (May 16, 2022). ### NetBox version v3.2.2 ### Feature type Change to existing functionality ### Proposed functionality The Changelog retention is not based on a date. All older then (your preference here) days will be removed (60 days in my case) I now came across an issue, that happened later than 60 days ago. I needed to know who created it and made the last update. This made me think, it might be useful to always keep the last 10 changelog items of an object, even if they are older than (60) days, and always keep the 'created' item. ### Use case Sometimes we need to see what happened to an object that had no changes in a long time. Who created it ? when was the last change and what was the change. If we keep the last 10 items and the creation log item, then we have good forensics to analyze problems in the past ### Database changes None ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:41:12 +01:00
adam closed this issue 2025-12-29 19:41:12 +01:00
adam commented 2025-12-29 19:41:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 16, 2022):

The Changelog retention is not based on a date. All older then (your preference here) days will be removed (60 days in my case)

60 days is a very low retention time. Why not set it to something much higher, or unlimited?

If we keep the last 10 items and the creation log item, then we have good forensics to analyze problems in the past

This wouldn't solve your problem. If there had been ten or more changes to the object already, you'd still have lost the initial creation record.

@jeremystretch commented on GitHub (May 16, 2022): > The Changelog retention is not based on a date. All older then (your preference here) days will be removed (60 days in my case) 60 days is a very low retention time. Why not set it to something much higher, or unlimited? > If we keep the last 10 items and the creation log item, then we have good forensics to analyze problems in the past This wouldn't solve your problem. If there had been ten or more changes to the object already, you'd still have lost the initial creation record.
adam commented 2025-12-29 19:41:14 +01:00
Author
Owner
Copy Link

@PieterL75 commented on GitHub (May 16, 2022):

Those were examples on what it could be useful for.
Having the last 10 entries will give some more visibility in the history and last modifications, even after a longer time

@PieterL75 commented on GitHub (May 16, 2022): Those were examples on what it could be useful for. Having the last 10 entries will give some more visibility in the history and last modifications, even after a longer time
adam commented 2025-12-29 19:41:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 16, 2022):

My point is that it's an arbitrary number and ultimately isn't going to be very useful. It sounds like #9160 would better suit your use case. Or, you could set CHANGELOG_RETENTION to zero to retain history indefinitely.

@jeremystretch commented on GitHub (May 16, 2022): My point is that it's an arbitrary number and ultimately isn't going to be very useful. It sounds like #9160 would better suit your use case. Or, you could set `CHANGELOG_RETENTION` to zero to retain history indefinitely.
adam commented 2025-12-29 19:41:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 16, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jul 16, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:41:14 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 15, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Aug 15, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#6481
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?