Since collecting of the /etc/migration-results is available in insights, we can have the statistics about usage of our tool. We can distinguish the use case by adding env variable. E.g. CONVERT2RHEL_INSIGHTS=1 for running the conversion from insights.

What we need:

• Add the env variable for each job (done under HMS-3421)
• Have the schema updated (used by team implementing the collecting of the file) https://github.com/oamg/schema-test/blob/main/breadcrumbs-schema-test.json
• Check if the migration-results file is generated every time
• Check if the env var is captured correctly and added to the file