-
Notifications
You must be signed in to change notification settings - Fork 681
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
[Core feature] Flyteadmin notifications: use webhooks APIs #2317
Comments
We are running flyte on-prem, and hence cannot use any of the existing notifications. |
We would also love to have more flexibility in the notification setup 👍🏻 |
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. |
It's crazy that we're in 2025 and the only option is still sending emails, which - as the author of this issue stated:
I totally agree on! There is a lot of overhead with domain verifications and so on, just to send a piece of text. At least support for Slack webhooks would be nice 🙄 |
Motivation: Why do you think this is important?
Currently flyteadmin notifications are delivered using the PagerDuty, Github and Slack email APIs. On AWS deployments FlyteAdmin uses SES to trigger emails, for all others the only alternative email implementation is SendGrid integration.
Setting up SES or SendGrid can be somewhat complicated. Furthermore, asking your Flyte users to configure the aforementioned services with email integrations adds even more overhead. It would be simpler as an alternative to provide webhook integration for notification so that users only have to configure existing API keys for PagerDuty/Github/Slack
Goal: What should the final outcome look like, ideally?
Setting up a flyteadmin deployment to send notifications should require simple configuration.
Describe alternatives you've considered
The current email API integration. We could introduce other email integrations to increase the accessibility of notifications.
Propose: Link/Inline OR Additional context
No response
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: