You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Implement some sort of messaging for when an assignment is successfully released. This can then be consumed by chat bots or automations from the scale lab users to either run JetSki on it or others.
Describe the solution you'd like
When we send the notification for the environment being ready we can as well send a msg via ZMQ or fedora-messaging .
The text was updated successfully, but these errors were encountered:
What if we just follow through with #405 and instead have an API that can be queried (or with webhooks) so people can manage their own notifications? That way they can just query the public QUADS API for the release status in a way they can customize and manage.
We could look to have a more robust assignment status page instead via something described in #368
We'd eventually have a message-bus driven implementation in the 3.0 QUADS roadmap however to replace our legacy stub/collections/email notifications.
Is your feature request related to a problem? Please describe.
Implement some sort of messaging for when an assignment is successfully released. This can then be consumed by chat bots or automations from the scale lab users to either run JetSki on it or others.
Describe the solution you'd like
When we send the notification for the environment being ready we can as well send a msg via ZMQ or fedora-messaging .
The text was updated successfully, but these errors were encountered: