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

fix: use __grafana_keyserver_datasource_type variable instead of its string value #77

Merged
merged 1 commit into from
Nov 16, 2024

Conversation

richm
Copy link
Contributor

@richm richm commented Nov 16, 2024

I think this line is supposed to use {{ __grafana_keyserver_datasource_alttype }}
like the grafana_7.ini.j2 template. At any rate,
{{ performancecopilot-valkey-datasource }} is not a variable, and not even a
valid variable name (cannot have - in a variable name.

Signed-off-by: Rich Megginson [email protected]

…string value

I think this line is supposed to use `{{ __grafana_keyserver_datasource_alttype }}`
like the grafana_7.ini.j2 template.  At any rate,
`{{ performancecopilot-valkey-datasource }}` is not a variable, and not even a
valid variable name (cannot have `-` in a variable name.

Signed-off-by: Rich Megginson <[email protected]>
Copy link
Contributor

@kurik kurik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @richm for the fix. I was facing the issue downstream as well, but have had no time to investigate it properly. This fix solved it.

@richm richm merged commit 10055ee into performancecopilot:main Nov 16, 2024
6 checks passed
@richm richm deleted the fix-valkey-ref branch November 16, 2024 17:13
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.

2 participants