Univention Bugzilla – Bug 53663
Verbose function in global.json, user.json and console logging
Last modified: 2021-08-16 13:54:20 CEST
A customer wanted to customize the logging output. He asked for the verbose parameter in the global.json and the users.json They seem to be out of function. # /usr/share/ucs-school-import/scripts/ucs-school-user-import --help -v, --verbose Enable debugging output on the console [default: False]. From Global configuration file reference =================================== "verbose": bool: if enabled, log output of level DEBUG will be send to the command line (stdout) ------- addition from the manual: Standard (boolean): true ---------------------------- Reading the Global reference from the server: Configuration files are read in a predefined order. Settings in later read configuration files overwrite settings from prior ones. The order is: 1. /usr/share/ucs-school-import/configs/global_defaults.json (do not edit) 2. /var/lib/ucs-school-import/configs/global.json (edit this) 3. Module specific configuration from /usr/share/ucs-school-import/configs/ (do not edit) 4. Module specific configuration from /var/lib/ucs-school-import/configs/ (edit this) 5. Configuration file set on the command line. 6. Options set on the command line by --set and its aliases. So the commandline parameter works kind of as expected. But is there any effect using the verbose parameter in the configuration file? If in the configuration file verbose is set, is this reseted to false by the commandline parameter? Because it is always the last switch and would overwrite it, but it is not possible to set verbose to no on the commandline. Or are the verbose Parameters in the configuration just for the http import? This would then be worth a note in the doc I haven't got it, how this works, so I'm not quite sure this is a bug, or just my not getting it. So a understandable explanation could solve the bug for me and the customer.