The rhc-worker-script is about to allow customers to specify environment variables in a configuration file. For the conversion use case, the variables need to be defined in /etc/rhc/workers/rhc-worker-script.yml.

Example of the yml file:

env:
  # environment variables to be set for the script
  FOO: "some-string-value"
  BAR: "other-string-value"
  # ...

Acceptance criteria:

• Verification confirms that with the latest rhc-worker-script scratch/brew builds customers can pass variables such as CONVERT2RHEL_OUTDATED_PACKAGE_CHECK_SKIP (or any other from https://github.com/oamg/convert2rhel/wiki/Environment-variables) to convert2rhel when converting through Insights
  • For instance when testing the CONVERT2RHEL_OUTDATED_PACKAGE_CHECK_SKIP variable, run the pre-conversion analysis Insights task on a system with some packages being outdated, see the inhibitor in the analysis result, then create the toml file, re-run the analysis, and the inhibitor should not be in the result anymore. Additionally, check that the variable is captured in the /etc/migration-results and the /etc/rhsm/facts/convert2rhel.facts breadcrumbs files.