No command-line facility for interrogating config options
Bug #1028839 reported by
Jonathan Lange
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Distributed Development |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
When debugging production issues, it's often useful to know what all of the config settings are set to. Because udd has many inferred config options, this cannot normally be done by inspecting a configuration file.
Presently, one must consult the config file (hoping, of course, that it's the right one!) and mentally reason from it, based on iconfig.py.
It would be much more useful if there were a command that simply dumped all of the configuration settings.
Revision history for this message
| Vincent Ladeuil (vila) wrote | #1 |
| Changed in udd: | |
| status: | New → Confirmed |
To post a comment you must log in.
That's what 'bzr config' is supposed to do.
The current implementation only support bzr files and a previous attempt to allow plugins register their own stacks/stores was rejected. See bug #823036.