Replica set check requires "clusterManager" database role

[aldeed]

Prerequisites

• Are you running the latest version?
• Are you able to consistently reproduce the issue?
• Did you search the issue queue for existing issue? Search issues

Issue Description

Reaction Identity waits before starting up to confirm that the MongoDB replica set is available. This check fails if the database user does not have "clusterManager" database role. We should not require this role in a deployed situation, especially not in production.

Steps to Reproduce

1. Start Reaction Identity Docker service with a MONGO_URL that specifies a user who does not have "clusterManager" database role.
2. View the service logs. It will hang for 2 minutes waiting for replica set, and then show a permission error.

Solution

This check was added primarily for development environments, where we are creating a replica set on the fly and Reaction Identity (Meteor) will throw an error if it isn't ready yet (race condition).

We can wrap the check in an environment variable that we set by default in development but would need to be manually set in a deployed environment.

Versions

3.0.0

[brent-hoover]

@aldeed Since this project is deprecated are we okay to close this?

[aldeed]

@zenweasel It's referring to this script, which might have been in some other projects, too. If you don't find similar code in any other projects, this should be okay to close.