-
Notifications
You must be signed in to change notification settings - Fork 93
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
Turn sinkFhirServerUrl off by default but on in e2e #1075
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1075 +/- ##
============================================
- Coverage 50.55% 50.44% -0.11%
+ Complexity 674 673 -1
============================================
Files 91 91
Lines 5519 5519
Branches 709 709
============================================
- Hits 2790 2784 -6
- Misses 2467 2473 +6
Partials 262 262 ☔ View full report in Codecov by Sentry. |
bf5d56e
to
84ee768
Compare
84ee768
to
3bd8c81
Compare
@mozzy11 FYI with this PR I am removing the sink FHIR-server from the default config but still enabling it for e2e. When you want to use this feature in your environment, please note this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @bashir2 for the changes. There is only one minor comment, you can merge the changes once it is resolved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the review @chandrashekar-s.
Description of what I changed
With #947 we have enabled sending FHIR resources to a sink server. Turning this on by default, requires an additional setup step of running a sink FHIR server which is not needed for most users (and also is an experimental feature). I am turning this off in the default config but turning it on in e2e since we have tests around it.
E2E test
TESTED:
Built and ran the docker image locally in the "off case"; relying on e2e for the "on case".
Checklist: I completed these to help reviewers :)
I have read and will follow the review process.
I am familiar with Google Style Guides for the language I have coded in.
No? Please take some time and review Java and Python style guides.
My IDE is configured to follow the Google code styles.
No? Unsure? -> configure your IDE.
I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)
I ran
mvn clean package
right before creating this pull request and added all formatting changes to my commit.All new and existing tests passed.
My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command
git pull --rebase upstream master