You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Add an option to delete history records of a VM giving a date or date range, so not all records are deleted.
Use case
This will be useful for VMs that have too many history records, but it's interesting to preserve some of them in case the user would want to have just the records for the past year / few months, for instance.
Interface Changes
This should be an additional option when using the --id option. The command could be:
onedb purge-history --id <ID> --end TIME. It would delete records from the oldest to the given time
onedb purge-history --id <ID> --start TIME --end TIME. It would delete records inside the given range
Additional Context
Related to this issue, where it was requested to purge records of a particular VM (already implemented with the --id option).
Progress Status
Code committed
Testing - QA
Documentation (Release notes - resolved issues, compatibility, known issues)
The text was updated successfully, but these errors were encountered:
Description
Add an option to delete history records of a VM giving a date or date range, so not all records are deleted.
Use case
This will be useful for VMs that have too many history records, but it's interesting to preserve some of them in case the user would want to have just the records for the past year / few months, for instance.
Interface Changes
This should be an additional option when using the
--id
option. The command could be:onedb purge-history --id <ID> --end TIME
. It would delete records from the oldest to the given timeonedb purge-history --id <ID> --start TIME --end TIME
. It would delete records inside the given rangeAdditional Context
Related to this issue, where it was requested to purge records of a particular VM (already implemented with the
--id
option).Progress Status
The text was updated successfully, but these errors were encountered: