Bug 1174069

Summary:	Merge config.yaml into params.json
Product:	[Community] Bugzilla	Reporter:	Sage Grigull <mgrigull>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4	CC:	jmcdonal, mail, mtahir, mtyson, qgong
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-29 05:47:36 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 Sage Grigull 2014-12-15 03:54:25 UTC

Description of problem:
At present application settings (not related to deployment) are stored in a config file /etc/rh-bugzilla/config.yaml.  In this setup it requires a deployment style process to update the configuration

Version-Release number of selected component (if applicable):
4.4.6028-5

How reproducible:
100%


Actual results:
requires deployment configuration change

Expected results:
should be accessible via application and configurable via bugzilla users with the relevant admin role.

Comment 1 Simon Green 2015-01-04 17:40:42 UTC

The reason we used a YAML file is that the contents were not a flat key value pair, as things were in the params file, but a complex data structure. Now that upstream has moved to params.json for it's configuration, it would make more sense to use that and ditch config.yaml.

Comment 2 Matt Tyson 🤬 2016-02-29 05:47:36 UTC


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