-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add webhook to "manually" start a plan #214
Comments
Hmm, I don't think backrest has a stable enough public API as of yet to expose anything explicit / make any promises on the API contract (and there are likely major refactors coming as I work towards multi-host management and am generally cleaning up tech debt). The workaround for this use case would be using restic directly and using the "Index Snapshots" button in the backrest UI to load your recent backup runs (but you lose out on Backrest's automatic prunes / notifications in that case). If you do want to code something to Backrest's API it's specified in the Backrest service https://github.com/garethgeorge/backrest/blob/main/proto/v1/service.proto#L32-L33 and you're welcome to codegen a library using connectrpc to call backrest's endpoints https://connectrpc.com/. You can see how the webui initializes it's transport here https://github.com/garethgeorge/backrest/blob/main/webui/src/api.ts#L1. |
I am also interested in the feature |
BTW, at one point @garethgeorge , you mentioned the |
Documented workaround at #275 . |
Describe the solution you'd like
Rather than starting a plan out of a cron, would be nice to trigger it from an API endpoint as a webhook.
This would allow other apps to trigger the backup when this other process is ending.
Additional context
I'm thinking of backing up immich when the Postgres backup is done and moved to the upload folder.
My DB backup script can curl the webhook to trigger the backrest plan.
The text was updated successfully, but these errors were encountered: