nextflow-io / nextflow-io/nextflow
Add support for custom key:value tags for files generated by Nextflow and stored in Azure and GCP cloud storage
Nobody has claimed this yet.
- Dominant language
- Groovy
- Stars
- 3.5k
- Forks
- 811
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 61
Description
Improvement
Currently, the Nextflow publishDir directive allows users to publish workflow files into a specific folder in cloud storage and (for Amazon S3 only as of writing) associate custom key:value tags with the published files.
As Nextflow is used across all the major cloud providers, it would be appropriate to support custom key:value tags in both Microsoft Azure and Google Cloud platforms.
Usage scenario
Resources generated by Nextflow pipelines can optionally have custom tags associated with them, and have that functionality consistent across the major cloud providers (not just Amazon S3 cloud storage).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Nextflow's publishDir handling for cloud storage and the existing Amazon S3 tag support. Compare the Azure and Google Cloud storage paths, then add equivalent custom key:value tag behavior and verify that published files retain tags on both providers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, gcp, groovy
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100