Describe the bug
I'm not sure if this is a bug with integreatly or banzaicloud, but the integreatly docs seem to mention support for this, so posting here initially.
When referencing sigv4_auth_enabled: true in the Grafana config block, the generated ConfigMap excludes the key.
Describe the bug I'm not sure if this is a bug with integreatly or banzaicloud, but the integreatly docs seem to mention support for this, so posting here initially.
When referencing
sigv4_auth_enabled: true
in the Grafana config block, the generated ConfigMap excludes the key.Steps to reproduce the issue:
Create the grafana-operator as normal;
And then create a Grafana resource using the CRD
Once applyed, the generated config is missing the
sigv4_auth_enabled
keyIf I add any other such as
disable_login_form = true
it will appear as expected, this issue seems to be specific tosigv4_auth_enabled
Expected behavior
I would expect for
sigv4_auth_enabled: true
to show under the[auth]
block within the configmapAdditional context The integreatly base CRD showing support for the key: https://github.com/integr8ly/grafana-operator/blob/fe0020ab7b75e59c28732a6a664fe8323a8c4246/config/crd/bases/integreatly.org_grafanas.yaml#L102