Open NickolausDS opened 3 years ago
I think this should move to the main gladier repo. Not sure if it can be done easily.
This can only be done within a running flow, since that's the only time a run_id will exist. The core gladier package can't really help with that. This needs to be done within a running flow, either by a funcx function or (probably much better) the expression evaluator: https://globus-automate-client.readthedocs.io/en/latest/globus_action_providers.html#simple-expression-evaluation
I see the problem with injecting it now.
On Tue, Jul 20, 2021 at 11:16 AM Nickolaus D. Saint < @.***> wrote:
This can only be done within a running flow, since that's the only time a run_id will exist. The core gladier package can't really help with that. This needs to be done within a running flow, either by a funcx function or (probably much better) the expression evaluator: https://globus-automate-client.readthedocs.io/en/latest/globus_action_providers.html#simple-expression-evaluation
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/globus-gladier/gladier-xpcs/issues/15#issuecomment-883521048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEFMPQ42HFGIW2XJLT3HEO3TYWOORANCNFSM5AV6GWPA .
The
$.context
variable in flows contains all the info we need to build a link to the Globus Webapp. We should add this to the metadata under a key likeflow_url
, and show it for pre-processed datasets until they've finished processing.