-
Notifications
You must be signed in to change notification settings - Fork 15
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
Bother Cromwell team until they implement notification #251
Comments
There's already a ticket open in Cromwell from more than 6 years ago. |
Update: that ticket is closed. Validate/document access to Cromwell-compatible API in CaaA It looks like CaaA will be the way in the future, and Cromshell may need to support (at least some usage scenarios of) that. |
What's CaaA?
…On Sat, Apr 15, 2023, 11:52 AM Steve Huang ***@***.***> wrote:
Update: that ticket is closed.
But two new are opened (needs appropriate login)
Validate/document access to Cromwell-compatible API in CaaA
<https://broadworkbench.atlassian.net/browse/WM-1909>
Email notifications for CaaA
<https://broadworkbench.atlassian.net/browse/WM-1910>
It looks like CaaA will be the way in the future, and Cromshell may need
to support (at least some usage scenarios of) that.
—
Reply to this email directly, view it on GitHub
<#251 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABD3RLFATX7DSK6NM6HI54LXBK74JANCNFSM6AAAAAAW5OZ7GA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Commenting on this thread because it would be a really great feature! |
This should really be there job. Let get them to do it for us!
Also, it must implement the DOOMED status or it's not complete.
The text was updated successfully, but these errors were encountered: