Description of problem:
Beaker-client now takes its configuration from ~/.beaker_client/config.
Please, modify it so that it will try to read some system-wide config file.
Settings from ~/.beaker_client/config should override system-wide settings.
Suggested config file:
Today I've noticed the global config seems to be already supported:
$ rpm -ql beaker-client | grep conf
$ head /etc/beaker/client.conf
# Hub xml-rpc address.
HUB_URL = "http://localhost/bkr"
# Hub authentication method. Example: krbv, password, worker_key
#AUTH_METHOD = "krbv"
AUTH_METHOD = "password"
# Username and password
#USERNAME = ""
#PASSWORD = ""
$ rpm -q beaker-client
Petr, quite right, currently bkr client checks the following locations for its config. The first one which exists is used:
Additionally, if BEAKER_CLIENT_CONF is set in the environment that file is used and the other logic is skipped.
What is missing is the overriding: if ~/.beaker_client/config exists, then the systemwide config is never read and settings in it will not apply, even if ~/.beaker_client/config does not define them.
Bulk reassignment of issues as Bill has moved to another team.
In particular, being able to inherit CA_CERT from /etc/beaker/client.conf would be quite useful for our setup. See bug 1258501.
*** Bug 1369994 has been marked as a duplicate of this bug. ***
Hi, I have create a pull request in https://github.com/beaker-project/beaker/pull/2 and fix it.
Thanks for the patch! I've uploaded a new version against develop here:
This bug fix is included in beaker-client-24.0-0.git.99.85d122d which is currently available for download here:
Beaker 24.0 has been released.