Dynamic resource labels - expanded options
acknowledged
Rob Newman
Expand support beyond
${workflowId}
and ${nextflowSessionId}
allowing users to assign additional variables as resource labels. This phase will broaden customization options to include the list below, empowering users with greater flexibility in tracking and estimating specific cost allocation metrics across different job configurations:
- ${workflowName}
- ${runName}
- ${userName}
- ${userId}
- ${userEmail}
- ${workspaceId}
- ${workspaceName}
- ${pipelineName}
Rob Newman
acknowledged
Rob Newman
Merged in a post:
Must tag all AWS resources as created by Nextflow and the billing user
B
Big Parrot
For accounting purposes, we must tag all resources created by Nextflow and Nextflow AWS Batch jobs with the username of the user who created the job. We need the tag to be called
billing
and the username of the user to be the value.We also need to tag all resources created by Forge with some identifying tag so that we can tune the permissions, i.e. so that we're not giving Nextflow permissions to destroy EFS filesystems used by the entire company and with vital data on them.
For accounting, we require that all resources created by NextFlow, including Spot instances, S3 buckets, compute environments, and anything that costs money, to be tagged with the username of the user who ran the job.
Rob Newman
Instances and resources can be tagged in the Seqera Platform since Enterprise release 22.3: they are currently limited in scope as they can only be applied to compute environments.
The current tagging system does not cover "username of the user who ran the job." because these are static values generated upon creating the compute environment in the Seqera Platform. A parametric/template tagging schema is planned.