You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the env provider ($__env{EXAMPLE}) the resulting value is incorrectly parsed when some special characters are in use, namely: # and ;. This is highlighted in the database configuration as causing potential problems here:
# If the password contains # or ; you have to wrap it with triple quotes. Ex """#password;"""
I attempted with both:
password: $__env{ENV_PASSWORD}
and a triple quote:
password: """$__env{ENV_PASSWORD}"""
The triple quote seems to cause more issues as it won't actually recognize the value in that case it seems like. This is remedied by changing the value to something that does not contain those special characters.
What did you expect to happen?
I expected that I would either be able to use the env provider with the special characters, or work around it using the documented workaround. However, it seems that neither are the case.
Did this work before?
No.
How do we reproduce it?
Set up a database user that has a password with special characters like # or ;
Attempt to connect grafana to that database instance using the env provider for the password
Is the bug inside a dashboard panel?
No response
Environment (with versions)?
Grafana: 7.3.9
OS: N/A
Browser: N/A
Grafana platform?
Kubernetes
Datasource(s)?
No response
The text was updated successfully, but these errors were encountered:
What happened?
When using the env provider (
$__env{EXAMPLE}
) the resulting value is incorrectly parsed when some special characters are in use, namely:#
and;
. This is highlighted in the database configuration as causing potential problems here:I attempted with both:
and a triple quote:
The triple quote seems to cause more issues as it won't actually recognize the value in that case it seems like. This is remedied by changing the value to something that does not contain those special characters.
What did you expect to happen?
I expected that I would either be able to use the env provider with the special characters, or work around it using the documented workaround. However, it seems that neither are the case.
Did this work before?
No.
How do we reproduce it?
#
or;
Is the bug inside a dashboard panel?
No response
Environment (with versions)?
Grafana: 7.3.9
OS: N/A
Browser: N/A
Grafana platform?
Kubernetes
Datasource(s)?
No response
The text was updated successfully, but these errors were encountered: