-
Notifications
You must be signed in to change notification settings - Fork 676
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
PoC for CID store annotations and workflow outputs structure #5885
base: cid-store
Are you sure you want to change the base?
Changes from all commits
de9a85d
0bbaae6
383560c
3b7102a
6444981
6bbaf35
aef7057
33d1db7
17f60e2
49df891
4548915
f92ee96
0033def
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -123,11 +123,15 @@ trait TraceObserver { | |
void onFlowError(TaskHandler handler, TraceRecord trace){} | ||
|
||
/** | ||
* Method that is invoked when a value is published from a channel. | ||
* Method that is invoked when a workflow output is published. | ||
* | ||
* @param name | ||
* The name of the workflow output | ||
* @param value | ||
* A list if the published channel was a queue channel, | ||
* otherwise an object if the channel was a value channel | ||
*/ | ||
void onWorkflowPublish(Object value){} | ||
void onWorkflowPublish(String name, Object value){} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is this the workflow run name? is it really necessary ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is the name of the workflow output, of which there can be several There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The name of workflow output target, right? it would be better declare it as
to no break the API There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Don't think that is needed because it is an undocumented preview feature (part of workflow outputs preview) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. It is the name given to the output in the workflow. We use it as key for the outputs map, and it is also used to refer to an specific output by cid:///#output. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Regarding the API change, let's move the discussion to #5909 which is the source of truth for this change |
||
|
||
/** | ||
* Method that is invoke when an output file is published | ||
|
@@ -150,4 +154,15 @@ trait TraceObserver { | |
void onFilePublish(Path destination, Path source){ | ||
onFilePublish(destination) | ||
} | ||
/** | ||
* Method that is invoked when a output file is annotated | ||
* @param destination | ||
* The destination path at `publishDir` folder. | ||
* @param annotations | ||
* The annotations attached to this file | ||
*/ | ||
void onFilePublish(Path destination, Path source, Map annotations){ | ||
onFilePublish(destination, source) | ||
} | ||
|
||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TODO: decide whether to use
tags
or phase it out in favor ofannotations