Bug 1369994

Summary:	Client configure file behaviour enhance
Product:	[Retired] Beaker	Reporter:	qhsong <qsong>
Component:	command line	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	ccui, dcallagh, mjia, rjoost
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-26 03:21:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***