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
Copy file name to clipboardexpand all lines: charts/fhir-server/README.md.gotmpl
+8-7
Original file line number
Diff line number
Diff line change
@@ -91,15 +91,16 @@ In addition to providing a default FHIR server configuration named template, thi
91
91
92
92
The deployer can specify a custom search parameters named template which will be used in the generation of the `extension-search-parameters.json` file by overriding the `extensionSearchParametersTemplate` chart value.
93
93
94
-
The deployer can specify custom datasource named templates which will be used in the generation of the `datasource.xml` and `bulkdata.xml` files by overriding the `datasourcesTemplate` chart value. The default for this chart value is a datasources template for a Postgres database, but this helm chart also provides named templates for Db2, Db2 on Cloud, and Derby databases in the `_datasourcesXml.tpl` file.
94
+
The deployer can specify custom datasource named templates which will be used in the generation of the `datasource.xml` and `bulkdata.xml` files by overriding the `datasourcesTemplate` chart value.
95
+
The default for this chart value is a template with datasources for a single Postgres database.
95
96
96
97
## Using existing Secrets for sensitive data
97
98
98
99
This helm chart specifies chart values for the following pieces of sensitive data:
99
100
100
-
- Database password or api key:
101
+
- Database user passwords:
102
+
- `db.adminPassword`
101
103
- `db.password`
102
-
- `db.apiKey`
103
104
- FHIR server user and admin passwords:
104
105
- `fhirUserPassword`
105
106
- `fhirAdminPassword`
@@ -113,13 +114,13 @@ These values can be specified directly in the `values.yaml` file, or the deploye
113
114
114
115
### Database password or api key
115
116
116
-
To have the `db.password` and `db.apiKey` values read from an existing Secret, the deployer must override the following chart values:
117
+
To have the `db.adminPassword` and `db.password` values read from an existing Secret, the deployer must override the following chart values:
117
118
118
119
- `db.dbSecret` - this is set to the name of the Secret from which the database information will be read
119
-
- `db.passwordSecretKey` - this is set to the key of the key/value pair within the Secret that contains the password
120
-
- `db.apiKeySecretKey` - this is set to the key of the key/value pair within the Secret that contains the api key
120
+
- `db.adminPasswordKey` - this is set to the key of the key/value pair within the Secret that contains the admin user password (for schema management)
121
+
- `db.userPasswordKey` - this is set to the key of the key/value pair within the Secret that contains the fhir-server's user password
121
122
122
-
If the `db.dbSecret` value is set, this helm chart will only look in the specified Secret for the password and api key. The `db.password` and `db.apiKey` chart values will be ignored.
123
+
If the `db.dbSecret` value is set, this helm chart will only look in the specified Secret for the passwords. The `db.adminPassword` and `db.password` chart values will be ignored.
0 commit comments