Move ConfigRevision from extras to core #8554

Closed
opened 2025-12-29 20:38:04 +01:00 by adam · 1 comment
Owner

Originally created by @jeremystretch on GitHub (Aug 31, 2023).

Proposed Changes

Move the ConfigRevision model from extras to core.

Justification

The active configuration and its revisions are considered core components of the application, as opposed to optional extensions.

Originally created by @jeremystretch on GitHub (Aug 31, 2023). ### Proposed Changes Move the ConfigRevision model from `extras` to `core`. ### Justification The active configuration and its revisions are considered core components of the application, as opposed to optional extensions.
adam added the status: acceptedtype: housekeeping labels 2025-12-29 20:38:05 +01:00
adam closed this issue 2025-12-29 20:38:05 +01:00
Author
Owner

@jeremystretch commented on GitHub (Dec 7, 2023):

I duplicated this under #14312 for v3.7. 🙄

@jeremystretch commented on GitHub (Dec 7, 2023): I duplicated this under #14312 for v3.7. :roll_eyes:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8554