You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix#299: allow specifying command-line values using config file
This required a number of coordinated changes to app startup:
- Argument processing (not parsing) was moved to the config module, including the expansion of the `mapped` users option the actual directory groups.
- Separation was done of bootstrap options, invocation options, and rule-processing options, so each could be given a single point of definition with app defaults.
- A new, optional `invocation_defaults` section was added to the main configuration file so the default values for all arguments could be specified there.
These changes led to resolution to a number of long-standing issues:
- There are no longer duplicate places where options have to be specified to get them added as rule-processing options and/or command-line arguments.
- The top-level logic doesn't get involved with the interaction of command-line arguments and configuration files, or be sensitive to the timing of configuration loading and argument processing.
- The logging of invocation now shows both the command-line arguments and their actual effect on the invocation options (including the formerly-hidden invocation options that actually override rule processing defaults).
- The names of various internal options are now matched to the names of the command-line arguments that override them, so the code is more readable throughout.
0 commit comments