Bug 1284341

Summary:	config.yaml needs to be removed
Product:	[Community] Bugzilla	Reporter:	Jeff Fearn 🐞 <jfearn>
Component:	Bugzilla General	Assignee:	Jeff Fearn 🐞 <jfearn>
Status:	CLOSED NEXTRELEASE	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	5.0	CC:	huiwang, mgrigull, mtahir, mtyson, qgong
Target Milestone:	5.0
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-12 00:38:17 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:
Bug Depends On:	1225107, 1324287, 1326559, 1326979, 1326981
Bug Blocks:

Description Jeff Fearn 🐞 2015-11-23 04:57:37 UTC

Description of problem:
This file should go away and the data should be either moved to the DB or the para.json file as appropriate.

Comment 1 Jason McDonald 2015-11-23 05:06:25 UTC

I vote for moving to the database and making it editable via the Admin UI so that editing the default bug description templates can be self-service for product owners.

Comment 2 Jeff Fearn 🐞 2015-11-23 05:09:30 UTC

(In reply to Jason McDonald from comment #1)
> I vote for moving to the database and making it editable via the Admin UI so
> that editing the default bug description templates can be self-service for
> product owners.

There is a separate bug for that specific component of config.yaml

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

*** Bug 1174069 has been marked as a duplicate of this bug. ***

Comment 6 Hui Wang 2016-03-22 07:37:23 UTC

Verified the issue.
version 5.0.2.rh2
The result is FAILED.

The config.yaml file still exist under data/ . 
The data, like doc_type_text, that you have mentioned in comment #3, should be moved to database or data/params.json, right?  I can see the data items you mentioned in comment #3 still exist in data/config.yaml.

Comment 7 Jeff Fearn 🐞 2016-04-25 23:58:04 UTC

This bug will be used to eliminate the code that loads and parses config.yaml

Comment 8 Jeff Fearn 🐞 2016-05-12 06:35:46 UTC

Hi Muhammad, the last remaining blocker for this bug is Bug 1225107 which is not in this sprint. What to do?

Comment 9 Muhammad Tahir 2016-05-13 00:28:58 UTC

Bug 1225107 moved to current sprint.

Comment 10 Rony Gong 🔥 2016-08-08 06:39:22 UTC

Tested on QA environment(5.0.3-rh4)
Result: Pass