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
We would like to implement a mechanism to allow Task submitters to specify a callback_url that will be used by TES to POST any change in status to the callback_url.
Requirements:
Task submitter must be able to specify a single callback_url as part of the TesRequest
TES will POST the full TesResponse to the callback_url on change in status using any (optional) auth headers
One thing to think about is whether the task submitter/client should be required/encouraged to send a secret alongside the callback_url that could then be sent back to the client together with the TesResponse. This might help prevent third parties from messing with task states.
We would like to implement a mechanism to allow Task submitters to specify a
callback_url
that will be used by TES to POST any change in status to thecallback_url
.Requirements:
callback_url
as part of the TesRequestcallback_url
on change in status using any (optional) auth headersRelated Issue: WES#133
The text was updated successfully, but these errors were encountered: