You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
from what I understand, private repositories and self-hosted git providers (e.g. self-hosted GitLab instance with private repos) are configured as text file pointed by the environment variable NXF_SCM_FILE.
This approach is not very flexible in some contexts such as a kubernets pod that acts as driver.
In few words, I have a Nextflow image that I spawn on k8s, with some secrets exposed as env variables.
Since I obviously cannot hardcode these secrets in the scm text file within the docker image, I need a custom script that write all parameters of my git provider into that file.
I think also that attaching a volume to the pod with the only purpose to make this file available is not very optimal.
Is it possibile to completely avoid the scm text file using only environment variables?
Or maybe someone already solve this issue in a more clever way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
from what I understand, private repositories and self-hosted git providers (e.g. self-hosted GitLab instance with private repos) are configured as text file pointed by the environment variable
NXF_SCM_FILE
.This approach is not very flexible in some contexts such as a kubernets pod that acts as driver.
In few words, I have a Nextflow image that I spawn on k8s, with some secrets exposed as env variables.
Since I obviously cannot hardcode these secrets in the scm text file within the docker image, I need a custom script that write all parameters of my git provider into that file.
I think also that attaching a volume to the pod with the only purpose to make this file available is not very optimal.
Is it possibile to completely avoid the scm text file using only environment variables?
Or maybe someone already solve this issue in a more clever way.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions