RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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.

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

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