Also changelog non-request-based changes #10445

Closed
opened 2025-12-29 21:31:32 +01:00 by adam · 1 comment
Owner

Originally created by @mulmat on GitHub (Nov 6, 2024).

NetBox version

v4.1.6

Feature type

Change to existing functionality

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

Currently, the handle_changed_object function bails out if the change does not originate from a request.

It would be desirable to log these changes as well.

Use case

We have added custom management commands that alter data, but the changes never appear in the change log.

Database changes

External dependencies

Originally created by @mulmat on GitHub (Nov 6, 2024). ### NetBox version v4.1.6 ### Feature type Change to existing functionality ### Triage priority I volunteer to perform this work (if approved) ### Proposed functionality Currently, the `handle_changed_object` function bails out if the change does not originate from a request. It would be desirable to log these changes as well. ### Use case We have added custom management commands that alter data, but the changes never appear in the change log. ### Database changes ### External dependencies
adam added the type: feature label 2025-12-29 21:31:32 +01:00
adam closed this issue 2025-12-29 21:31:32 +01:00
Author
Owner

@jeremystretch commented on GitHub (Dec 5, 2024):

Change logging unfortunately is not something that can be implemented in a blanket fashion. You'll need to employ the change logging context manager explicitly within your custom logic if you rely on its functionality.

@jeremystretch commented on GitHub (Dec 5, 2024): Change logging unfortunately is not something that can be implemented in a blanket fashion. You'll need to employ the change logging context manager explicitly within your custom logic if you rely on its functionality.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#10445