-
Notifications
You must be signed in to change notification settings - Fork 0
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
Output file path not specified #9
Comments
We also need it to know what data entities to add to metadata / e.g. WfExS outputs a crate that contains quite a bit of stuff including but not limited to the outputs defined by the workflow and stage file. When adding outputs to the main crate, I'm currently proposing we add that entire output in Really, in addition to that folder in general as a |
I don't think all the outputs from WfExS should need to appear again in this crate if that is included as a sub-crate. It is fine to not reference all the files from a crate, you may just describe the folder for instance. And then "lift" the particular outputs to the Trusted crate's Action - it's consumer do not need to know that those outputs are also in the nested "as-is" crate from WfExS. This is also probably easier as the nested action would have the different ID compared to the original request. (You can link those with |
@stain We are currently trying to get the HutchAgent to write the Wfexs stage file using the incoming Trusted Workflow Run Crate plus the Workflow Run Crate from Workflow Hub once a DownloadAction has occured. |
There is no way currently to get the output file path from the incoming crate. It is needed for the Wfexs stage file to be generated.
The text was updated successfully, but these errors were encountered: