Bug 1530919 - [RFE]Include a vars directory instead of only single config.yml file and not hard code the path
Summary: [RFE]Include a vars directory instead of only single config.yml file and not ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-metrics
Classification: oVirt
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.2
: 1.1.3
Assignee: Shirly Radco
QA Contact: Lukas Svaty
URL:
Whiteboard:
Depends On:
Blocks: 1475135
TreeView+ depends on / blocked
 
Reported: 2018-01-04 07:44 UTC by Shirly Radco
Modified: 2018-04-09 06:17 UTC (History)
3 users (show)

Fixed In Version: ovirt-engine-metrics-1.1.3-1.el7ev
Clone Of:
Environment:
Last Closed: 2018-03-29 11:07:06 UTC
oVirt Team: Metrics
Embargoed:
rule-engine: ovirt-4.2?
rule-engine: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 86792 0 master MERGED ansible: add config.yml.d directory 2018-01-31 12:40:04 UTC

Description Shirly Radco 2018-01-04 07:44:09 UTC 
Description of problem:
Add a directory /etc/ovirt-engine-metrics/config.yml.d and read all *.yml files from it. 
This way a program can add a file there automatically without overwriting a user's manual changes.

Also, have the patch to oVirt metrics config.yml file. Process by make and use PKG_SYSCONF_DIR.
Comment 1 Yaniv Kaul 2018-01-04 08:47:38 UTC 
Is this a CodeChange (and why do we need a BZ for it?)
If it's RFE, it's lacking the '[RFE]' prefix we use.
what is the target milestone?
Comment 2 Yaniv Kaul 2018-01-11 13:33:25 UTC 
Pushing to 4.2.2. If it's ready before - great.
Comment 3 Lukas Svaty 2018-03-07 14:16:25 UTC 
verified in ovirt-engine-metrics-1.1.3.2-1.el7ev.noarch
Comment 4 Sandro Bonazzola 2018-03-29 11:07:06 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.
Note You need to log in before you can comment on or make changes to this bug.