-
Notifications
You must be signed in to change notification settings - Fork 685
Include WorkflowMetadata in lineage records #6069
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
Draft
jorgee
wants to merge
1
commit into
master
Choose a base branch
from
lineage-workflow-metadata
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think it would be preferable to keep as much as possible aligned to WorkflowMeta structure, in the same way as it's done in the tower client
nextflow/plugins/nf-tower/src/main/io/seqera/tower/plugin/TowerClient.groovy
Line 620 in 5bfe1c1
we could consider removing repeated values in the parent object
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.
Not sure if I get your comment.
If I am not wrong, in
TowerClient
, theworkflow
is a plain map that contains everything that is inWorkflowMetadata
, removing stats and adding other properties like the resolved config and params.If we do the same and include everything as property of the
WorkflowRun
class, it will be very difficult to maintain, so I prefer to keep it inside themetadata
property (or rename it to another name). If a new parameter is added in the WorkflowMetadata, it will also be added to the 'metadata' without any model update.A small difference is the
sessionId
andname
that are properties inWorkflowRun
and they were also in theWorkflowMetadata
map. I do not see a problem with keeping it inmetadata
and removing it fromWorkflowRun
. We can also add the resolved config if you think it is better.The big difference is in the
workflow
andparams
. I think they are the parts that mainly describe theWorkflowRun
, and, in theTowerClient
, they are spread in a set of properties. Inworkflow
, we already included the information that is inscriptFile
,scriptName
,scriptId
,repository
,commitId
. I have just added other info (revision
,projectName
andmanifest
) that I think they are describing the workflow more than the execution. In fact, I think theworkflow
description could have a separate record, and LID and just have a reference in theWorkflowRun
.