WHMCS Katapult module expire backups

[krystal-gitbase]

Katapult's API has the ability to schedule a disk backup policy to be deleted at a specific future time, to also erase all existing backups attached to the policy at that time:

https://developers.katapult.io/docs/dev/core/delete-disk-backup-policy-schedule

Currently when WHMCS sets up a VM on Katapult it creates a basic disk backup policy for the VM to take one daily backup.
However, when the VM is subsequently deleted the disk backup policy is left in place (this is native Katapult behaviour, for Katapult purposes a chargeable disk backup policy is retained separately to the VM it was backing up to allow the user to opt to restore it at a later point if they wish). Because there is then no further involvement by any user, this backup policy is then left in place forever.

Could we enhance the WHMCS module to make use of the above endpoint such that when a VM is deleted, the module can also instruct Katapult to expire the backup?

For our own use within our own WHMCS module, this can be hard-configured to always expire the backup at a date/time 30 days after the deletion takes place. Ideally however this should also be incorporated into the public module as a configurable value, the default should be to not set backups to be purged (the current behaviour) but with the option to schedule them for purging a configurable number of days in the future.

---

This issue was created by GitBase for ticket #983.

• Reported by: Alex Easter
• Originally reported at: October 31, 2024 13:44
• GitBase Ticket ID: 983
• View ticket on GitBase