8000 feat: default email alert group by grutt · Pull Request #547 · hatchet-dev/hatchet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: default email alert group #547

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

Merged
merged 20 commits into from
Jun 3, 2024
Merged

Conversation

grutt
Copy link
Contributor
@grutt grutt commented May 31, 2024

Description

When new users join, there is no alerting configured by default. While this is the intended behavior for things like workflow runs which may be noisy, it may be problematic for alerts for token expiration.

This change adds additional configuration settings for alerts and exposes the tenant member list as a special email group.

Type of change

  • New feature (non-breaking change which adds functionality)

What's Changed

  • add tenant alert setting configuration to enable workflow run failure and token expiration alerts
  • add tenant configuration to enable tenant member email alert group
  • add query to get emails for a tenant
  • update alerters with config
  • expose config on ui

Copy link
vercel bot commented May 31, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hatchet-docs 🛑 Canceled (Inspect) Jun 3, 2024 3:19pm

@grutt
Copy link
Contributor Author
grutt commented May 31, 2024

image

@grutt grutt marked this pull request as ready for review May 31, 2024 20:42
grutt and others added 2 commits June 3, 2024 08:10
Co-authored-by: abelanger5 <belanger@sas.upenn.edu>
@abelanger5 abelanger5 merged commit 207f1bb into main Jun 3, 2024
19 checks passed
@abelanger5 abelanger5 deleted the feat--default-email-alert-group branch June 3, 2024 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0