DRIVERS-2577: add a runCommand specification

[nbbeeken]

Link to github generated document

Process meta:

• DRIVERS-2577 is repurposed to both remove the RW concern options for the UTF and add the runCommand spec
• A following PR will use the driver epic number (DRIVERS-2533) to track the new runCursorCommand spec

---

Adds a specification for the existing runCommand API. Generally, it summarizes requirements across the specifications and links the reader to the more detailed specification on the subject. Adds language that encourages drivers to not inspect nor modify user input, drivers will have to assess their current implementation and determine how that guidance can best be
followed.

Test coverage is targeted at each subject in the spec inspecting command construction is performed as expected. For example, a new test asserts that a database configured with a RC will not attach read concern fields to the user's command document per the spec.

Removing Read Concern and Write Concern settings from the runCommand unified test operation because they intentionally are not supported and no tests have been written to use them.

Please complete the following before merging:

• Update changelog.
• Make sure there are generated JSON files from the YAML test files.
• Test changes in at least one language driver.
  • Node.js: feat(NODE-5207): deprecate unsupported runCommand options and add spec tests node-mongodb-native#3643
• Test these changes against all server versions and topologies (including standalone, replica set, sharded clusters, and serverless).
  • Probably need to adjust runOnRequirements still

[jmikola]

You'll need to add useMultipleMongoses: true in the client entity definition to avoid flaky test failures.

Per failPoint in the Unified Test Format spec:

The client entity SHOULD specify false for useMultipleMongoses if this operation could be executed on a sharded topology (according to runOnRequirements or test.runOnRequirements). This is advised because server selection rules for mongos could lead to unpredictable behavior if different servers were selected for configuring the fail point and executing subsequent operations.

[nbbeeken]

I think you meant to say set it to false, per the spec right? changed it

[jmikola]

Oy, typo on my part. Yes, I meant useMultipleMongoses: false.

[jmikola]

Suggested change

	- topologies: [ replicaset, sharded-replicaset, load-balanced, sharded ]
	minServerVersion: '4.4'
	- minServerVersion: "4.0"
	topologies: [ replicaset ]
	- minServerVersion: "4.2"
	topologies: [ sharded-replicaset, load-balanced ]

Not sure why minServerVersion: 4.4 was used, but other transaction tests allow 4.0+ replica sets and 4.2+ sharded clusters.

Specifying sharded-replicaset and sharded together also seemed redundant.

I don't think sharded should be used for any spec tests that require successfully executing a transaction since an oplog is needed. It looks like there are a few instances of tests requiring sharded instead of sharded-replicaset. I'll open a separate JIRA ticket about that.

[nbbeeken]

Updated, and thanks for clearing that up

[jmikola]

Just to close the loop here, I created DRIVERS-2609 to clear up other spec tests.

[jmikola]

I also POC-ed the tests in PHPLIB: mongodb/mongo-php-library#1066