Bother Cromwell team until they implement notification
lbergelson opened this issue · 4 comments
lbergelson commented
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.
SHuang-Broad commented
There's already a ticket open in Cromwell from more than 6 years ago.
I'll see if I can make any tractions.
SHuang-Broad commented
Update: that ticket is closed.
But two new are opened (needs appropriate login)
Validate/document access to Cromwell-compatible API in CaaA
Email notifications for 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.
lbergelson commented
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:
***@***.***>
mamelara commented
Commenting on this thread because it would be a really great feature!