process.exit(0) in v2.2.0 tasks limit programatic usage

[gsears]

Hi all,

While probably well-intentioned, introducing process.exit(0) in #113 in the various tasks has limited the ability to call the code programatically. In our case, we do a lot of integration testing on the db with our main schema applied to it. As we have a considerable amount of migrations, it is not viable to rerun all migrations from scratch, so we pull a docker container with our latest version-control schema and apply local migrations to this during development (considerably speeding up the workflow).

To achieve this we have the following jest setup script:

import dotenv from 'dotenv';
import { runTaskByName } from '@fauna-labs/fauna-schema-migrate/dist/tasks';
import { createClient } from './libs/fauna';

dotenv.config();

module.exports = async () => {
  const client = createClient(process.env.FAUNADB_SECRET)();
  // @ts-expect-error 2339 Make client available for teardown
  global.client = client;
  try {
    await runTaskByName('apply', 'all', []);
    console.log('Applied migrations');
  } catch (err) {
    console.error(err);
    process.exit(1);
  }
};

This was working fine in the previous version, but the introduction of the following code kills our test setup when no migration changes are needed (therefore all the test suites that follow!)

// tasks/apply.ts
   } else {
      printMessage(`     ✅ Done, no migrations to apply`, 'success')
      process.exit(0) // Problematic
    }

I guess a solution would be to do a check for migration differences using retrieveMigrationInfo or something similar to conditionally trigger the apply task, though this would essentially be doing duplicate work already done in the apply function.

Obviously this is a niche usecase, and I definitely don't want to impede the healthy development and refactoring of the tool, but I wonder if this was 'sugar' or if it is due to other changes. I've only had a cursory look at the source code, so might have missed something!

What was the rationale for the change? Would these process.exit() calls be able to be reverted?

Thanks!