[SERVER-11143] Use Constraints in Option Parsing Created: 11/Oct/13  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Internal Code
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor - P4
Reporter: Shaun Verch Assignee: Backlog - Security Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-10255 Refactor storage of command line options Closed
is related to SERVER-8510 Move command line parsing into MONGO_... Closed
Assigned Teams:
Server Security
Participants:

 Description   

The "Constraint" class represents a constraint on an option. It isn't being used heavily now, but eventually all our option validation should be done through constraints. This will make the description of our options completely declarative which will make it easier to verify and document.



 Comments   
Comment by Githook User [ 06/Dec/13 ]

Author:

{u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}

Message: SERVER-11143 Added support for specifying that a string option must be of a specified format
Branch: master
https://github.com/mongodb/mongo/commit/6bef7b4fa2b5648e11da5aeb4f44b2f6bae7952d

Comment by Githook User [ 18/Nov/13 ]

Author:

{u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}

Message: SERVER-11143 Add constraints for dependencies between options
Branch: master
https://github.com/mongodb/mongo/commit/4de74f61147f576477618af17a4014b6a325023f

Comment by auto [ 04/Nov/13 ]

Author:

{u'username': u'Zarkantho', u'name': u'Shaun Verch', u'email': u'shaun.verch@10gen.com'}

Message: SERVER-11143 Add constraints to option registration interface
Branch: master
https://github.com/mongodb/mongo/commit/0b1f32bd5e8adf5e56396f001ac97d0200146ff6

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