FI-3604 Run evaluate without test kit using tmp dir

[Shaumik-Ashraf]

Summary

Run inferno execute without being in a test kit by automatically spinning up the required services and putting Docker mounts in a temporary directory. After a release with this PR a user should be able to do:

inferno evaluate ./path/to/package.tgz

Testing Guidance

1. Checkout this branch
2. Run the evaluator in a "test kit" (with services)

bundle
bundle exec inferno services start
bundle exec ./bin/inferno evaluate ./spec/fixtures/uscore311.tgz
bundle exec inferno services stop

3. Make a temporary directory with a Gemfile of inferno core pointing to this branch to run the evaluator outside of a test kit:

Example Gemfile

# frozen_string_literal: true

source "https://rubygems.org"

gem "inferno_core", "~> 0.6.9", github: 'https://github.com/inferno-framework/inferno-core', branch: 'fi-3604-evaluator-tmp-dir'

Example command:

bundle exec inferno evaluate path/to/spec/fixtures/uscore311.tgz

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.00%. Comparing base (726496f) to head (2fafd6c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #674   +/-   ##
=======================================
  Coverage   85.00%   85.00%           
=======================================
  Files         303      303           
  Lines       13677    13677           
  Branches     1760     1760           
=======================================
  Hits        11626    11626           
  Misses       2043     2043           
  Partials        8        8           

Flag	Coverage Δ
backend	91.57% <ø> (ø)
frontend	79.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[dehall]

Is it possible to run inferno "globally" without needing a gemfile in the current directory?

[Jammjammjamm]

Is it possible to run inferno "globally" without needing a gemfile in the current directory?

The Gemfile is only needed for this PR, because you have to point at this branch rather than a released gem.

[Jammjammjamm]

Won't data_path need to be updated to an absolute path prior to changing the working directory?

[Shaumik-Ashraf]

fixed

[Jammjammjamm]

Why is this logic only needed for the fhirpath service? I would expect it to be present for the validator service as well, or just a plain docker compose up without the service names.

[Shaumik-Ashraf]

The validator service doesn't expose its port so it doesn't conflict with spinning it up for the evaluator. On the other hand if we wanted the evaluator to leverage an already running validator service we would have to route it through Nginx or modify test kits to expose the validator port as well.

[Jammjammjamm]

This change prevents users from customizing the database configuration, which is a necessary feature. Also, the config directory is not included in the inferno_core gem.

[Shaumik-Ashraf]

I reverted this line and added a new database config specifically for the evaluator that uses sqlite in memory.