Configuration based on flags needs help
Registered by
Vish Ishaya
Configuration based on flags has some annoying issues. This proposes that we design a clearer method for configuration of the system.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Vish Ishaya
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
Configuration options via flags have the following issues:
* usage of lags for configuraton is unexpected, and not very discoverable for new users
* syntax for flagfiles is non-standard for configurations
* flags from lazy loaded modules don't show up in --help
Some cleanup here needs to be done. At the very least, we need flags to show up in --help. If there is an easy way to convert to a more obvious and standard config file format, that would also be a fine solution.
This should hopefully be fixed by:
https:/
(?)
