Should we allow job authors to exit with arbitrary exit codes?

From @lakhassane: We had a situation in a client implementation where we had 5 operations in the same job.
But we had to NOT EXECUTE any of the 5 operations if we received a certain username. Throwing an error was not an option either. So we need to allow the user to exit the job with a specific code.

Using process.exit(0) would allow us to exit as the exit code might be also relevant in platform.

This new helper function can be used to do so but we are not yet sure of the security implications.

example of usage

fn(state => {
  if (true) {
    console.log('exiting with code 42');
    exit(42);
  }
  console.log('keep going')
  return state;
});

See https://github.com/OpenFn/language-common/pull/32 for more details

Start by reviewing the referenced OpenFn/language-common pull request #32 and the job execution behavior around the proposed exit helper. Determine the security and runtime implications of allowing arbitrary exit codes, then document a decided interface and acceptance criteria for supported behavior.