[SERVER-54617] Create a resmoke configuration management helper Created: 18/Feb/21  Updated: 29/Oct/23  Resolved: 02/Mar/21

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.9.0

Type: Task Priority: Major - P3
Reporter: Raiden Worley (Inactive) Assignee: Raiden Worley (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from SERVER-53814 Separate MongoDB config from resmoke Closed
Backwards Compatibility: Fully Compatible
Sprint: STM 2021-03-08
Participants:
Story Points: 3

 Description   

Right now a lot of different places modify resmoke's global configuration and the configs for spawned processes. These are stored in raw python dicts. We should create a dict-like configuration class that manages these configs, storing every access or update, and lets us view the history. We should also be able to assert the consistency of the configuration. This will reduce the risk in large changes to fixtures.

(As a bonus, this will make it easier for people updating fixtures, suite definitions, etc to understand how the mongo/d finally gets run.)



 Comments   
Comment by Githook User [ 02/Mar/21 ]

Author:

{'name': 'Carl Raiden Worley', 'email': 'carl.worley@10gen.com', 'username': 'aggrand'}

Message: SERVER-54617 Create a resmoke configuration management helper
Branch: master
https://github.com/mongodb/mongo/commit/8082beefe8259cbd909fcaab4b8a1fcf3eae7cb1

Comment by Raiden Worley (Inactive) [ 01/Mar/21 ]

For reference, this ticket ended up creating a --exportMongodConfig advanced option for resmoke, outputting a yaml with the history, optionally including location of accesses.

Generated at Thu Feb 08 05:34:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.