New introspection `workflow.seqeraPlatform` scope for data from Seqera Platform about nextflow

[pditommaso]

-1. it platform that needs to orchestrate nextflow, not the other way around

[bentsherman]

I believe the main use case was to apply resource labels based on platform metadata such as the run ID and user. These settings would be defined in the platform (e.g. CE-level config) but you still need to expose this metadata to the config via an implicit variable or environment variable

[pditommaso]

Then platform should provide the corresponding config

[ewels]

Then platform should provide the corresponding config

That's exactly what I'm suggesting. That platform provides the config to Nextflow, via workflow variables.

These should 100% be read-only, the same as the other workflow introspection variables.

[pditommaso]

It's not clear what we are trying to solve with this?

[ewels]

We want to allow Nextflow users to make use of metadata that comes from Seqera Platform, in a read-only manner, within Nextflow scripts.

Example use cases:

• Using a Platform username within a publishing file-path
• Sending custom emails from the pipeline to the email address of the Platform user

I can find more if needed by going back to the Platform customers who requested it if you'd like.

[ewels]

Here's the original feature request, though I think I've seen it elsewhere as well: https://feedback.seqera.io/feature-requests/p/nextflow-needs-to-be-able-to-access-metadata-from-the-tower