No action needs to be done. Just note that the config server no longer upconverts the writeConcern of any incoming requests from internal connections to "majority" if no writeConcern is provided. All internal command requests to the config server are expected to provide a writeConcern.

Description of Linked Ticket

This code is incompatible with catalog shards and after discussions can be removed. This will probably be a multi step process:

• Make sure any calls that might use this code path are explicitly specifying the writeConcern
• assert the above behaviour i.e if check if there are any edge cases we missed
• remove the code
• downstream attention (mongorestore, automation agent etc etc)