Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[grafana] support templating grafana ini options #253

Merged
merged 3 commits into from
Mar 1, 2021

Conversation

bbetter173
Copy link

Addresses the same issue as #201 but works.

Only difference in output is whitespace output when nil values are supplied.

@bbetter173 bbetter173 changed the title Feature/grafana config tpl [grafana] Feature/grafana config tpl Mar 1, 2021
@bbetter173 bbetter173 changed the title [grafana] Feature/grafana config tpl [grafana] support values.yaml template in grafana ini options Mar 1, 2021
@bbetter173 bbetter173 changed the title [grafana] support values.yaml template in grafana ini options [grafana] support templating grafana ini options Mar 1, 2021
…l templating.

Signed-off-by: Ben Bettridge <bbettridge@switch.tv>
Signed-off-by: Ben Bettridge <bbettridge@switch.tv>
Signed-off-by: Ben Bettridge <bbettridge@switch.tv>
@bbetter173 bbetter173 force-pushed the feature/grafana-config-tpl branch from 786b94e to 8b5a1fa Compare March 1, 2021 05:58
@BadgerOps
Copy link

BadgerOps commented Apr 1, 2021

Hi folks - commenting here but we could probably chat over in #335 - I'm curious why this change was merged with no updates to documentation? This broke the documented method of how to insert the grafana.ini into the values.yaml, which is causing issues for me. I don't mind changing my values if the documentation in this repo is updated to align with the purpose of this change.

Thanks!

Edit: would still like to see some documentation on this, but after doing some more digging this PR actually exposed an invalid configuration that wasn't erroring out for me before.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants