Skip to content
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

Support success notification for integration with https://healthchecks.io/ #635

Open
ryanwinter opened this issue May 15, 2024 · 4 comments

Comments

@ryanwinter
Copy link

Would love a feature where you could add a call to an external service such as https://healthchecks.io/ when the backup is successful so that I could keep track of failures that may have happened.

@gaul
Copy link
Owner

gaul commented May 18, 2024

Duplicate of #427. I am happy to add this functionality, does #427 (comment) work with healthchecks.io?

@gaul gaul closed this as completed May 18, 2024
@ryanwinter
Copy link
Author

Thanks for the response!

I think it's a different purpose and implementation. I was looking at more a notification that a backup had occurred successfully, either with an email, or in healchecks case, ping a URL.

@gaul gaul reopened this May 19, 2024
@ryanwinter
Copy link
Author

Was thinking about this a bit more, and it might honestly be a bit difficult. Because having a single callback for the entire endpoint wouldnt be that useful, because you would likely have multiple jobs pushing into different buckets.

So then you would need to create a mapping of bucket to callback endpoint, which you would need to either pass in via environment variables, or have a config file that's consumed.

@gaul
Copy link
Owner

gaul commented Aug 13, 2024

S3Proxy was created with a 1:1 mapping for frontend-backend which is simple but perhaps not the best approach for users who want more advanced options, e.g., single S3 endpoint which maps buckets to different backend providers, middlewares, etc. I guess we could extend the configuration to M:N although haven't had a defined use case yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants