Error handling in db/migrations/migrate.initDB

[slmyers]

Errors do not seem to be properly caught in the promise chain. Investigate.

function initDB(config) {
  const masterMapping   = mapper.generateMasterMapping(mapper.gatherScreenerMappings());
  testConnect(config.client)
  // master index and mappings
  .then(utils.initIndex(config.client, config.masterIndex))
  .then(utils.initMapping(config.client, config.masterIndex, config.masterTypeName, masterMapping))
  // response index and mappings
  .then(utils.initIndex(config.client, config.responseIndex))
  .then(utils.initMapping(config.client, config.responseIndex, config.responseTypeName, responseMapping))
  .then(initPercolators(config.client, config.masterIndex))
  .catch( e => {
    console.log(`exiting with ${e}`);
    process.exit(1);
  })
}

[slmyers]

Problem may lie in the utils package and how these functions are returned:

function mappingExists(elasticClient, indexName, typeName) {
  return elasticClient.indices.existsType({
    index: indexName,
    type: typeName
  });
}

This only returns a promise, but perhaps it should be thened and resolved or rejected.