-
Notifications
You must be signed in to change notification settings - Fork 420
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
Remove Sentieon license details from -profile test #1237
Conversation
|
conf/base.config
Outdated
withLabel: 'sentieon' { | ||
ext.sentieon_auth_mech_base64 = secrets.SENTIEON_AUTH_MECH_BASE64 | ||
ext.sentieon_auth_data_base64 = secrets.SENTIEON_AUTH_DATA_BASE64 | ||
} |
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.
I wouldn't put that in base.config
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.
OK so I'll move it to conf/sentieon.config
.
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.
I'd do that in a separate config dedicated to sentieon licence
Moved to separate file |
nextflow.config
Outdated
@@ -137,6 +137,9 @@ params { | |||
// Load base.config by default for all pipelines | |||
includeConfig 'conf/base.config' | |||
|
|||
// Load Sentieon config | |||
includeConfig 'conf/sentieon.config' |
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.
It seems to me that with that, you wouldn't be able to run anything without having SENTIEON_AUTH_MECH_BASE64
and SENTIEON_AUTH_DATA_BASE64
set as nf-secrets.
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.
How so? if these aren't set, surely it just ignores them?
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 this work:
process {
withLabel: 'sentieon' {
ext.sentieon_auth_mech_base64 = secrets.SENTIEON_AUTH_MECH_BASE64 ?: ''
ext.sentieon_auth_data_base64 = secrets.SENTIEON_AUTH_DATA_BASE64 ?: ''
}
}
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.
No, that is actually the problem. By referring to those two secrets in cache.config
without them being set, Ram got
Unknown config secret 'SENTIEON_AUTH_MECH_BASE64'
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.
Do they need to be secret? Can we just make them params?
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.
You write too fast 😆 "No, that is actually the problem." was my answer to "How so? if these aren't set, surely it just ignores them?".
This
ext.sentieon_auth_mech_base64 = secrets.SENTIEON_AUTH_MECH_BASE64 ?: ''
seems to work. In fact, it could probably just have been introduced in the orginial cache.config
and then problem solved.
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.
But what if you need SENTIEON_AUTH_MECH_BASE64 but you are running for real? It's not just a test thing, it's for extra security: https://support.sentieon.com/appnotes/license_server/
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.
Hmmm - I didn't know about that "License Server Extension". It is not something we use at my workplace. Perhaps make an issue for making Sarek handle that as well?
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.
Isn't that what this is for? What's the point in these variables?
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.
This just in from Ram: He still gets
Unknown config secret 'SENTIEON_AUTH_MECH_BASE64' -- Check script
when using
ext.sentieon_auth_mech_base64 = secrets.SENTIEON_AUTH_MECH_BASE64 ?: ''
ext.sentieon_auth_data_base64 = secrets.SENTIEON_AUTH_DATA_BASE64 ?: ''
in cache.config
and commercial-license (ie. only SENTIEON_LICENSE_BASE64 as nf-secret)
Tested this branch locally by running and I got this error back
|
@@ -433,6 +433,30 @@ mutect2: | |||
- tests/csv/3.0/recalibrated_tumoronly.csv | |||
- tests/test_mutect2.yml | |||
|
|||
## Sentieon |
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.
Will this not cause the pytests for sentieon to be run twice?
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.
agree, we don't need that to run twice.
Maybe it was added just to trigger it
Darn, the ternary doesn't work. I've wrapped it in a parameter now |
Oh hold on, I messed up by leaving the old config in there 🤦 |
This is painful. I guess now they are failing since Perhaps there is an environmental variable or something we can use to detect if we are on CI? 🤔 |
yeah, so I'd rather we deal with profile tests with a specific profile. |
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).