Summary

Atlas Server prohibits the getParameter command, which is needed to evaluate the serverParameters field in runOnRequirement.

We should document this limitation and clarify how test runners should deal with it (e.g. avoid enforcing serverParameters, assume any expected serverParameters cannot be matched).

Motivation

Who is the affected end user?

Drivers.

How does this affect the end user?

Test runners may receive a server-side error from Atlas Serverless, such as "{getParameter: '*'} not allowed in this atlas tier".

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

Depending on how drivers have implemented runOnRequirement evaluation, this may happen all the time (e.g. due to caching server parameters) or only when serverParameters is specified.

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

Server-side error may interrupt test execution.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes.