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
The current mechanism puts the database connection string (including username and password) in the process stack where it is viewable by anyone on the system. This is somewhat undesirable- though I don't know precisely what harm could come, general "best practices" would suggest we improve this.
I've done a little work and it looks like we may be able to specify database connection parameters in a file separate from the general Cromwell config (e.g. fh-slurm-sing-cromwell.conf) and use HOCON's includedirective:
include required(classpath("application"))
include required(file("database.conf"))
###### FH Slurm Backend, with call caching, without docker/singularity
....
The path above doesn't have to be in the current directory- my understanding is that we could specify any path for that, though I'm not sure if things like "~" are expanded.
The text was updated successfully, but these errors were encountered:
This makes things a bit more awkward and requires people to customize more in the way that I'm looking at this now. I need to figure out how to pass the path to the database.conf to the java command so it knows where to look for it in cromServer.sh. If I could figure that out, then it'd be awesome and totally doable.
The current mechanism puts the database connection string (including username and password) in the process stack where it is viewable by anyone on the system. This is somewhat undesirable- though I don't know precisely what harm could come, general "best practices" would suggest we improve this.
I've done a little work and it looks like we may be able to specify database connection parameters in a file separate from the general Cromwell config (e.g.
fh-slurm-sing-cromwell.conf
) and use HOCON'sinclude
directive:Where
database.conf
contains thedatabase
section as specified by Cromwell:The path above doesn't have to be in the current directory- my understanding is that we could specify any path for that, though I'm not sure if things like "~" are expanded.
The text was updated successfully, but these errors were encountered: