-
Notifications
You must be signed in to change notification settings - Fork 157
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
Make the static datasource option the default #1694
Labels
Milestone
Comments
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhirSharedLib Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhirSharedLib Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhirSharedLib Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhirSharedLib Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhir jars from the fhirSharedLib and move the definition from server.xml into the corresponding datasource dropinConfigs (this way we can only include the drivers that will actually be used) 3. stop excluding fhir-core and fhir-config from our webapps since they're no longer in the shared lib 4. other minor dependency tweaking to avoid packaging derby with our webapps Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 25, 2021
1. rework the user's guide 2. remove the fhir jars from the fhirSharedLib and move the definition from server.xml into the corresponding datasource dropinConfigs (this way we can only include the drivers that will actually be used) 3. stop excluding fhir-core and fhir-config from our webapps since they're no longer in the shared lib 4. other minor dependency tweaking to avoid packaging derby with our webapps Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 26, 2021
1. rework the user's guide 2. remove the fhir jars from the fhirSharedLib and move the definition from server.xml into the corresponding datasource dropinConfigs (this way we can only include the drivers that will actually be used) 3. stop excluding fhir-core and fhir-config from our webapps since they're no longer in the shared lib 4. other minor dependency tweaking to avoid packaging derby with our webapps Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Feb 28, 2021
1. rework the user's guide 2. remove the fhir jars from the fhirSharedLib and move the definition from server.xml into the corresponding datasource dropinConfigs (this way we can only include the drivers that will actually be used) 3. stop excluding fhir-core and fhir-config from our webapps since they're no longer in the shared lib 4. other minor dependency tweaking to avoid packaging derby with our webapps Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 1, 2021
Remove exclusions while still avoiding packaging the db drivers into the webapp Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 2, 2021
1. Remove references to enabling the proxy datasource from the user's guide 2. Remove the datasource-proxy.xml configDropin example 3. Stop packaging fhir-peristence-jdbc (and its dependencies) in the shared resources lib 4. Mark the enabledProxyDatasource and jdbc-level dataSourceJndiName as deprecated Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
lmsurpre
added a commit
that referenced
this issue
Mar 2, 2021
1. Remove references to enabling the proxy datasource from the user's guide 2. Remove the datasource-proxy.xml configDropin example 3. Stop packaging fhir-peristence-jdbc (and its dependencies) in the shared resources lib 4. Mark the enabledProxyDatasource and jdbc-level dataSourceJndiName as deprecated Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Attempted scenarios where fhir-server-config.json was not properly migrated away from fhirProxyDatasource. Sample log messages: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
In #916 we introduced a new static datasource option. Now I'd like that to be the default.
This will enable us to follow OpenLiberty docker image recommendations (e.g. see #923), use the newer maven-based liberty dev mode support, and potentially even run on other application servers.
Describe the solution you'd like
The default IBM FHIR Server image should use a static datasource approach which leverages configDropins to easilly add an remove tenant-based datasource definitions.
Describe alternatives you've considered
Keep using our FHIRProxyDatasource as the default.
The text was updated successfully, but these errors were encountered: