Bug 1369994 - Client configure file behaviour enhance
Summary: Client configure file behaviour enhance
Keywords:
Status: CLOSED DUPLICATE of bug 844364
Alias: None
Product: Beaker
Classification: Retired
Component: command line
Version: develop
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 02:34 UTC by qhsong
Modified: 2016-11-14 00:06 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-26 03:21:51 UTC
Embargoed:


Attachments (Terms of Use)

Description qhsong 2016-08-25 02:34:36 UTC
Description of problem:
Hi, I just recently use `beak` to test our system. I think the client configure files behaviour may not work as my expect.
Beaker file have two files: "~/.beak_client/config" and "/etc/beaker/config".Client only use one of them to apply.I think it seems strange.Can Beaker behaviour like `git config`.
`/etc/beaker/config` is a global default config for all users, and "~/.beak_client/config" is user config.User config can override global config when client start.

If you want to change to this mode, I can do a pull request in Github to modify this.

Comment 1 Dan Callaghan 2016-08-26 03:21:51 UTC
A patch for this would be very welcome.

*** This bug has been marked as a duplicate of bug 844364 ***


Note You need to log in before you can comment on or make changes to this bug.