CLA Assistant fails to start when used with AWS DocumentDB

[Daniel Dyla]

Recently, my team tried to update our instance of CLA Assistant. We are hosting it in a docker container in ECS backed by a DocumentDB instance. The CLA document src/server/src/documents/cla.js indexes all fields with a wildcard index, which causes a server error from AWS DocumentDB, which does not support text indexes. This causes an unhandled promise rejection at application startup. In our previous version, this caused an application log but did not otherwise cause problems. #823 updated the node version used in the Dockerfile to 16 which causes unhandled promise rejections to crash the application.

I am asking for one of the following:

1. Add an option to disable creating the index
2. Handle the promise rejection from index creation so as not to crash the application
3. Create a targeted index instead of a wildcard index https://www.mongodb.com/docs/manual/core/indexes/index-types/index-wildcard/

I am happy to submit a PR for any of these ideas if they would be accepted.

[Luckymhe]

If PR failed the CLA assistant what will Happen?

[Daniel Dyla]

If PR failed the CLA assistant what will Happen?

This has nothing to do with the CLA check its about self hosting the assistant