Bug 1835168

Summary:	Allow split config file
Product:	Red Hat Enterprise Linux 8	Reporter:	Yedidyah Bar David <didi>
Component:	grafana	Assignee:	Andreas Gerstmayr <agerstmayr>
Status:	CLOSED DEFERRED	QA Contact:	Jan Kurik <jkurik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	agerstmayr, jkurik, mgoodwin, mperina, nathans
Target Milestone:	rc	Keywords:	FutureFeature, Triaged
Target Release:	8.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-20 13:59:12 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:
Bug Blocks:	1835177

Description Yedidyah Bar David 2020-05-13 09:55:14 UTC

Description of problem:

For various reasons, both management/packaging and security, it's useful to be able to have the configuration split to separate files - e.g. to allow software to manage a specific file for its own configuration, for users to be able to add their stuff without having to update the main file (which can/should(?) be overwritten on upgrades), etc.

See also upstream issue about this [1], and in particular the comments I wrote there about how I think it should behave.

[1] https://github.com/grafana/grafana/issues/17653

Comment 1 Andreas Gerstmayr 2020-05-25 15:49:27 UTC

A change like this has to happen in upstream - I'll ping a Grafana maintainer next week (they are busy with GrafanaCon at the moment, which lasts until Friday) if they're willing to accept a PR for this feature.
If yes, I can work on a PR to implement this feature in the RHEL 8.4 timeline.

Comment 2 Andreas Gerstmayr 2020-09-16 13:00:14 UTC

fyi, no response from upstream so far: https://github.com/grafana/grafana/issues/17653#issuecomment-650284732

Comment 5 Andreas Gerstmayr 2021-10-20 13:59:12 UTC

As there is no response from upstream so far [1] whether they're interested in that feature and are willing to accept a PR, I'll close this ticket.
It's a big change, and we don't plan to deviate from upstream in that regard.

If this gets implemented upstream at some point, it'll land in RHEL via our regular rebases of Grafana.
In the meantime, I'd recommend using the Ansible ansible.builtin.assemble module [2] or something similar to merge multiple configuration files into one.


[1] https://github.com/grafana/grafana/issues/17653
[2] https://docs.ansible.com/ansible/latest/collections/ansible/builtin/assemble_module.html