FI-2337: add disableDefaultResourceFetcher to fhir_resource_validator.cliContext defaults #456
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds the new HL7 validator wrapper cliContext setting
disableDefaultResourceFetcher
to our cliContext defaults. This depends on hapifhir/org.hl7.fhir.core#1526 but can be merged in before that because the hl7 validator wrapper ignores any unrecognized options. (confirmed against the production instance at https://validator.fhir.org/ )Full details on this setting are available on the ^ linked PR, but it prevents fetching of unknown profiles and extensions, for example when a resource reports a profile in
meta.profile
that is not part of the IG under test. The Inferno validator wrapper does not fetch these profiles so this setting makes the hl7 wrapper match the inferno wrapper in that regard.Testing Guidance
Here are the usual notes on using the hl7 validator wrapper:
hl7_validator_service
indocker-compose.background.yml
andnginx.background.conf
fhir_resource_validator
instead ofvalidator
and make sure it points to the hl7 wrapper. An easy place to do this is in the demo suitedev_suites/dev_demo_ig_stu1/demo_suite.rb
: