-
Notifications
You must be signed in to change notification settings - Fork 598
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use a remote config in kuberun #2781
Conversation
Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me overall. Just a few small things and then we'll be ready to merge:
- please address my comments below
- add the new options to the Nextflow kuberun docs
- confirm that you've tested this feature on your k8s cluster
@@ -248,7 +248,7 @@ class K8sDriverLauncher { | |||
.setProfile(cmd.profile) | |||
.setCmdRun(cmd) | |||
|
|||
if( !interactive && !pipelineName.startsWith('/') ) { | |||
if( !interactive && !pipelineName.startsWith('/') && !cmd.remoteProfile && !cmd.runRemoteConfig ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would just checking cmd.runRemoteConfig
be sufficient here?
…ith config Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
7d9b10f
to
ed1be19
Compare
@bentsherman can you please start the checks manually? The CI Pipeline seems not to start automatically. |
@pditommaso Can you tell why the CI tests aren't running? I can't trigger them manually. It just says "Waiting for status to be reported", I don't know what that means. |
it may be related to this change 6e23e03. @jorgeaguileraseqera any clue? |
The PR action is not started automatically: nextflow-io#2781 It seems to be related to nextflow-io@6e23e03
I think this PR should fix it: #2796 |
The PR action is not started automatically: nextflow-io#2781 It seems to be related to nextflow-io@6e23e03 Signed-off-by: Lehmann-Fabian <fabian.lehmann@informatik.hu-berlin.de>
Using kuberun with remote configs is not yet possible. Therefore, I added the option to use a config file only located in the cluster.