Add workflow.report config scopes#6812
Conversation
✅ Deploy Preview for nextflow-docs-staging canceled.
|
|
Could this impact any Platform capabilities? just wondering and better e2e testing |
|
It shouldn't break platform runs that use the existing report options, since this PR falls back to them if For platform runs that use the new |
d9fa5cd to
d752bc2
Compare
f0808c2 to
204f45c
Compare
Signed-off-by: Ben Sherman <bentshermann@gmail.com>
204f45c to
446e2c2
Compare
|
On second thought, I'm not sure if we should continue to build on these reports. I think it would be better to just expose the raw data (trace events, lineage) and let external systems (agents, seqera platform) render this information to the user however they want Maybe we should just deprecate these built-in reports and move them into a plugin |
This PR adds the
workflow.reportconfig scope as a replacement for the existing report scopes:dag->workflow.report.dagreport->workflow.report.executiontimeline->workflow.report.timelinetrace->workflow.report.traceThe config settings are otherwise identical, except that the
fileoption is resolved against the workflow output directory instead of the launch directory.This makes the standard reports easier to use with workflow outputs.