Use Case

As a... Mongoose developer
I want... to keep up with necessary CI changes
So that... the integration tests keep working as expected

User Experience

Maintainers of mongoose need to be able to maintain tooling that starts clusters for FLE tests with minimal effort.  DET is notoriously flaky - we need a strategy to ensure that changes don't break Mongoose's CI.

Dependencies

• none

Risks/Unknowns

• Can we unpin driver evergreen tools in general? How do we prevent them from unexpectedly breaking the mongoose CI? If we don't unpin, how do we ensure they get updated on a regular enough basis?
  • Should drivers-evergreen-tools adopt semver?

Acceptance Criteria

Implementation Requirements

• Investigate possible approaches to managing drivers-evergreen-tools in mongoose.  Consider:
• Discuss approaches with Val to choose an approach that satisfies his requirements.
• File a ticket to implement the strategy, if necessary.

Testing Requirements

• n/a

Documentation Requirements

• n/a

Follow Up Requirements

• file ticket (see AC)