Feature #18621
Updated by Peter Amstutz 3 months ago
Deleting past versions should leave a record in the audit trail. Would like to be able to provide a filter that describes past versions that should be pruned. I think the interface would end up being very similar to the bulk trash API (#20972), where it deletes a page of things at a time. This would probably have a distinct endpoint as the behavior will be a bit different. There's a couple ways to approach this: one would be to set @trash_at@ and @delete_at@ on the past versions and have the normal cleanup process actually delete the rows. The main issue is that when certain changes happen on the head version, it updates @trash_at@ and @delete_at@ in all the past versions in @sync_past_versions@. So we would need to decide what we want the behavior to be in that situation. The other option is to just delete the rows immediately.