-
Notifications
You must be signed in to change notification settings - Fork 5
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
Add an option to filter out subworkflows in specific Cromwells #698
Add an option to filter out subworkflows in specific Cromwells #698
Conversation
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 looks great, thanks!
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.
Nit: if the purpose of the new config option is just to not include sub-workflows in some cases, I think naming the option IS_CROMIAM is confusing (unless you anticipate other logic will need to change based on whether or not CromIAM is involved).
@rsasch |
That name works for me, but I think it should be |
Great, thanks! TIL that by default Terra shows sub-workflows on the job details page, since we prefer the opposite in daily operations 😄 |
Reason
In general, we are deploying JMUI against a Cromwell instance that uses OAuth (an OIDC based AuthProxy) but does not have CromIAM. This is affected by #576 that subworkflows are showing up in the job details page.
See discussion here: https://broadinstitute.slack.com/archives/CFA6Q2QBU/p1599146973203800?thread_ts=1599145468.201200&cid=CFA6Q2QBU
Changes
Add a
INCLUDE_SUBWORKFLOWS
flag and set it toTrue
by default so subworkflows are filtered out by default as well. non-CromIAM Cromwell backends that are using OAuth should set it toFalse
.