cfg: allow some options to be required
Registered by
Mark McLoughlin
There may be cases where we can't have a sensible default for a config option and the user absolutely must specify a value for them.
We should be able to mark an option as required by doing e.g.
StrOpt('foo', required=True)
See bug #983734 for where this came up, although it looks like the options in that case weren't actually required
Blueprint information
- Status:
- Complete
- Approver:
- Mark McLoughlin
- Priority:
- Medium
- Drafter:
- Mark McLoughlin
- Direction:
- Approved
- Assignee:
- Mark McLoughlin
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
folsom-1
- Started by
- Mark McLoughlin
- Completed by
- Mark McLoughlin
Related branches
Related bugs
Sprints
Whiteboard
Addressed by: https:/
cfg: allow options to be marked as required
(?)
