Bug 1174069 - Merge config.yaml into params.json
Summary: Merge config.yaml into params.json
Keywords:
Status: CLOSED DUPLICATE of bug 1284341
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-15 03:54 UTC by Sage Grigull
Modified: 2025-10-16 23:39 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-29 05:47:36 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1225107 1 None None None 2025-10-16 23:40:52 UTC

Internal Links: 1225107

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 ***
Note You need to log in before you can comment on or make changes to this bug.