(SA) Adapt command registry to support both router and shard commands (SERVER-78976)

[SERVER-80434] CommandRegistry per Service Created: 25/Aug/23  Updated: 29/Oct/23  Resolved: 11/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0

Type: Sub-task Priority: Major - P3
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-79945 mqlrun tests are sensitive to unrelat... Closed
depends on SERVER-80847 reinforce MONGO_LOGV2_DEFAULT_COMPONE... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2023-08-07, Service Arch 2023-08-21, Service Arch 2023-09-04, Service Arch 2023-09-18
Participants:

 Comments   
Comment by Githook User [ 11/Sep/23 ]

Author:

{'name': 'Billy Donahue', 'email': 'billy.donahue@mongodb.com', 'username': 'BillyDonahue'}

Message: SERVER-80434 Support multiple Services, associate a CommandRegistry per Service
Branch: master
https://github.com/mongodb/mongo/commit/40b4e5d7702b79b59196ab717b4da7abcf88616c

Comment by Billy Donahue [ 07/Sep/23 ]

logging from headers would help identify command roles, so slight detour to handle SERVER-80847 (a mechanical change) to re-enable that capability.

Generated at Thu Feb 08 06:43:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.