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.

Sign up for GitHub

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

Jump to bottom

Create notification templates for key events #13328

Open
1 of 23 tasks
dannykopping opened this issue May 21, 2024 · 2 comments
Open
1 of 23 tasks

Create notification templates for key events #13328

dannykopping opened this issue May 21, 2024 · 2 comments
Assignees
@dannykopping
Labels
feature Something we don't have yet
Milestone
Notifications Sub...

Comments

@dannykopping
Copy link
Contributor

dannykopping commented May 21, 2024 •
edited
Loading

Note: notifications should not be sent to the user which initiated the event.

Workspace events

All of these events will go to the resource owner.

  • marked dormant
  • marked for deletion
  • queued for deletion
    • 72h warning
    • 24h warning
    • 30m warning
  • deleted
  • automatic build failure
  • automatically updated

Template events

  • deprecated (receiver: owner)
  • manual build failure
  • automatic build failure (receiver: template admin)

Account events

  • user account created (receiver: user admin)
  • user account deleted (receiver: user admin)
  • user account suspended/reactivated (receiver: user admin, user)
  • password reset (receiver: user)
  • user email verification (receiver: user)

Deployment events

All of these events will go to administrators only.

  • access URL unhealthy
  • database connection unhealthy
  • DERP unhealthy
  • provisioner daemons unhealthy
  • websockets unhealthy
  • wsproxy unhealthy
@coder-labeler coder-labeler bot added the chore Non-customer facing refactors, cleanup, or technical debt. label May 21, 2024
@dannykopping dannykopping mentioned this issue May 21, 2024
Open
43 tasks
@dannykopping dannykopping added feature Something we don't have yet and removed chore Non-customer facing refactors, cleanup, or technical debt. labels May 21, 2024
@dannykopping dannykopping self-assigned this Jun 3, 2024
@michaelbrewer
Copy link
Contributor

I assume "All of these events will go to the resource owner", is the user that created a the workspace about to expire?

@dannykopping
Copy link
Contributor Author

@michaelbrewer that is correct 👍

@dannykopping dannykopping mentioned this issue Jun 11, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dannykopping dannykopping

Labels
feature Something we don't have yet
Projects
None yet
Milestone
Notifications Subsystem: System-Gener...
Development

No branches or pull requests
2 participants
@dannykopping @michaelbrewer