Summary
It would be useful to let the post-backup webhook only run after applying the retention policy for use cases like shutting down the target after a backup.
Motivation / Use case
In my current setup I am running weekly backups to an offsite target. It gets powered on at a specific time, the backup is performed shortly after that and at the end of the backup I shut the target down via a custom post-backup webhook. This approach works reliable and consistent for quite some time now but I noticed that the retention policy was never applied.
The cause for this is that my webhook shuts the target down right after the backup finished but before the policy can be applied. As a workaround, I added a fixed delay in my shutdown webhook. However, the actual time needed in undeterministic so that I have to use a delay which is longer than needed to make sure the policy is done running before the shutdown triggers.
Proposed solution
For my use case, I would like to trigger the webhook only after the retention policy was applied instead of right after the actual backup finished. The easiest way would probably be to add a toggle like "Apply rentention policy before webhook" whereas the more flexible way would be to add a separate webhook for this case or, like for the notifications, define webhooks once and then add them to certain trigger points within each backup job.
Impact
Low
Summary
It would be useful to let the post-backup webhook only run after applying the retention policy for use cases like shutting down the target after a backup.
Motivation / Use case
In my current setup I am running weekly backups to an offsite target. It gets powered on at a specific time, the backup is performed shortly after that and at the end of the backup I shut the target down via a custom post-backup webhook. This approach works reliable and consistent for quite some time now but I noticed that the retention policy was never applied.
The cause for this is that my webhook shuts the target down right after the backup finished but before the policy can be applied. As a workaround, I added a fixed delay in my shutdown webhook. However, the actual time needed in undeterministic so that I have to use a delay which is longer than needed to make sure the policy is done running before the shutdown triggers.
Proposed solution
For my use case, I would like to trigger the webhook only after the retention policy was applied instead of right after the actual backup finished. The easiest way would probably be to add a toggle like "Apply rentention policy before webhook" whereas the more flexible way would be to add a separate webhook for this case or, like for the notifications, define webhooks once and then add them to certain trigger points within each backup job.
Impact
Low