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
While I was spinning up a new deployment of the FHIR server, the schematool did not run properly, because of an = character in the database password.
java.lang.IllegalArgumentException: Property must be defined as key=value, not: password=abcdefgh0123=567
at com.ibm.fhir.schema.app.Main.addProperty(Main.java:2196)
at com.ibm.fhir.schema.app.Main.parseArgs(Main.java:2011)
at com.ibm.fhir.schema.app.Main.main(Main.java:2790)
As you can see, this also makes the schematool print the password in clear text to the logs.
We create our databases via a Kubernetes Postgres Operator, which creates random password strings. I changed that user's password afterwards by replacing the = with a - which solves the issue.
I am not sure, if quoting the values on the command line would solve this – if not, this is probably a bug in the schema conversion tool itself (rather than in the Helm chart), isn't it?
Cheers,
Johannes
The text was updated successfully, but these errors were encountered:
While I was spinning up a new deployment of the FHIR server, the schematool did not run properly, because of an
=
character in the database password.As you can see, this also makes the schematool print the password in clear text to the logs.
We create our databases via a Kubernetes Postgres Operator, which creates random password strings. I changed that user's password afterwards by replacing the
=
with a-
which solves the issue.I am not sure, if quoting the values on the command line would solve this – if not, this is probably a bug in the schema conversion tool itself (rather than in the Helm chart), isn't it?
Cheers,
Johannes
The text was updated successfully, but these errors were encountered: