Configurable naming strategy for Wave in Studios
Esha Joshi
Currently, when customizing and building a Studio with conda, Wave uses a hardcoded
imageSuffix
naming strategy, which creates nested repository paths (e.g., community.wave.seqera.io/data-studios/jupyter/numpy_scipy_tqdm_pip_pruned:7dc3ba408fd1df3c
). Whereas with Nextflow, Wave uses the none
strategy by default.This causes issues when:
- Lacking ECR permissions to create repositories (ecr:CreateRepository)
- Needing consistency with Nextflow workflows that use different naming strategies
We should enable configuration of the container image naming strategy in Wave Studios to support different registry requirements and structure constraints.
I think there's two options:
- Env variable (specified at CE level or elsewhere)
WAVE_STUDIOS_NAMING_STRATEGY=tagPrefix
- Configmap option (for self-hosted)
wave:
studios:
namingStrategy: tagPrefix # none, tagPrefix, or imageSuffix