We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug Allocate Tenant without TenantKey Fails in the ibm-fhir-schematool on db2
Environment Which version of IBM FHIR Server? 4.7.1
To Reproduce Steps to reproduce the behavior:
docker run ibm-fhir-schematool:latest-debug --tool.behavior=onboard --db.host=localhost \ --db.port=50000 --user=db2inst1 --password=change-password --db.database=fhirdb \ --sslConnection=false --db.type=db2 --schema.name.fhir=CLINIC3 --grant.to=testuser \ --tenant.name=ic3
$?
Expected behavior Allocation should complete with exit code 0 and then proceed to test-tenant
Additional context Reported by Client
The text was updated successfully, but these errors were encountered:
Allocate Tenant without TenantKey Fails in the ibm-fhir-schematool on…
3a328bc
… db2 #2349 Signed-off-by: Paul Bastide <pbastide@us.ibm.com>
PR #2351
Sorry, something went wrong.
Merge pull request #2351 from IBM/issue-2349
76fc05f
Allocate Tenant without TenantKey Fails in the ibm-fhir-schematool on db2 #2349
Verified behavior via docker run of ibm-fhir-schematool with db2 on ibmcloud
(output at run conclusion) 2021-05-14 18:28:55.098 00000001 INFO com.ibm.fhir.schema.app.Main SCHEMA CHANGE: OK
prb112
No branches or pull requests
Describe the bug
Allocate Tenant without TenantKey Fails in the ibm-fhir-schematool on db2
Environment
Which version of IBM FHIR Server?
4.7.1
To Reproduce
Steps to reproduce the behavior:
$?
and it returns 1 which is unexpected.Expected behavior
Allocation should complete with exit code 0 and then proceed to test-tenant
Additional context
Reported by Client
The text was updated successfully, but these errors were encountered: