Add virtual machine support and calendar-based scheduling (closes #14, #15)#18
Merged
Merged
Conversation
Closes #14 and #15. Maintenance plans can now target either a Device or a VirtualMachine, and scheduling supports days/weeks/months/quarters/years with an optional anchor_date for drift-free calendar schedules (e.g. start of each quarter). - models: nullable device + new virtual_machine FK with per-target conditional uniqueness; frequency_unit and anchor_date fields; get_next_maintenance_date() honors the anchor to avoid drift. - migration 0003 adds the new schema, forward-compatible (existing day-based plans keep working with default frequency_unit='days'). - forms / tables / templates surface a unified Target column with Device / VM badges, plus a human-readable Frequency and Anchor. - new VirtualMachine detail-page extension + dedicated VM tab view. - API serializers and filtersets expose virtual_machine, frequency_unit, anchor_date and target_type; legacy device fields remain nullable for backward compatibility. - version bumped to 1.4.0, CHANGELOG updated. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #14 and #15.
Maintenance plans can now target either a Device or a VirtualMachine, and scheduling supports days/weeks/months/quarters/years with an optional anchor_date for drift-free calendar schedules (e.g. start of each quarter).