[DRIVERS-2278] getParameter is not supported on Atlas Serverless Created: 14/Apr/22 Updated: 27/Oct/23 Resolved: 15/Apr/22 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Unified Test Runner |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Unknown |
| Reporter: | Jeremy Mikola | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Not Needed | ||||||||
| Description |
SummaryAtlas 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). MotivationWho 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. |
| Comments |
| Comment by Jeremy Mikola [ 15/Apr/22 ] |
|
There is nothing to address here. Atlas Serverless intentionally prohibits access to getParameter. I only encountered this error because the new project for DRIVERS-1967 was misconfigured. That has since been fixed by the cloud team and instances created within the new project now have access to getParameter. |