-
Notifications
You must be signed in to change notification settings - Fork 875
Notify on workspace creation/update #15845
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
Comments
cc @mtojek |
@DanielleMaywood I also added "workspace update". where the workspace is edited, and perhaps parameters are changed. is this possible too? |
@bpmct RE "workspace update": I think I have some queries. What do we consider to be "updating" a workspace? There are a few different actions that can result in changes to a workspace's underlying data. Do we intentionally keep this scope very narrow? If so, that makes this much easier as there are fewer places where we need to trigger the notification. |
Relates to #15845 When the `/workspace/<name>/builds` endpoint is hit, we check if the requested template version is different to the previously used template version. If these values differ, we can assume that the workspace has been manually updated and send the appropriate notification. Automatic updates happen in the lifecycle executor and bypasses this endpoint entirely.
Hey, apologies I missed your message 2 weeks ago. Yes, we can mark this one as completed 🎉 |
Some customers want to create automations once a workspace has been created. By adding notification/websocket triggers for when a workspace has been created or updated, this is possible via a lambda.
TwoThree notification typesUnderlying metadata:
The text was updated successfully, but these errors were encountered: