Summary

Currently mongomirror tests (and I think mongosync’s?) use a pinned version of mongo-orchestration. That version seems to predate recent changes in upstream where `start-orchestration.sh` no longer requires/accepts a parameter to define the mongo-orchestration home.

We need a way to use up-to-date mongo-orchestration but also preserve our workflow where we can instantiate any of a number of server versions. I think we need the binaries to have been separately downloaded; we currently provide them via an `orchestration.config` file in our mongo-orch home dir (which we set as our repo root).

Motivation

Who is the affected end user?

C2C/TAR

How does this affect the end user?

We’re pinned to an old mongo-orch version and can’t seem to make the latest one work. We’re not blocked, but we’re also “marooned”.

How likely is it that this problem or use case will occur?

Happens every time.

If the problem does occur, what are the consequences and how severe are they?

It’s a bit annoying because if we somehow don’t load that pinned version of the repo then someone has to figure out their mistake, which can take a while.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

C2C/TAR

Is this ticket only for tests?

yes

Acceptance Criteria

We need a way to preserve our existing workflow.