This is an automated email from the ASF dual-hosted git repository.

zky pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git


The following commit(s) were added to refs/heads/main by this push:
     new 0480d35461 External Grafana in HelmSetup.md (#652)
0480d35461 is described below

commit 0480d3546190b28d496a7c9be100eeb78463853c
Author: Rob Heckel <[email protected]>
AuthorDate: Sat Oct 7 21:32:32 2023 -0500

    External Grafana in HelmSetup.md (#652)
    
    The documentation for the external Grafana doesn't match the values in the 
helm chart.
    Move from `grafana.useExternal` and `grafana.externalUrl`
    to
    `grafana.enabled` and `grafana.external.url`
---
 docs/GettingStarted/HelmSetup.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/GettingStarted/HelmSetup.md b/docs/GettingStarted/HelmSetup.md
index 33fee37691..f5c477700c 100644
--- a/docs/GettingStarted/HelmSetup.md
+++ b/docs/GettingStarted/HelmSetup.md
@@ -270,8 +270,8 @@ The secret name needs to be the same as the value 
`option.connectionSecretName`
 
 Yes, the devlake helm chart supports using an external Grafana. You can set 
the following values while installing from helm:
 
-- `grafana.useExternal`: this should be `true`
-- `grafana.externalUrl`: use your Grafana's URL, e.g. 
`https://grafana.example.com`
+- `grafana.enabled`: this should be `false`
+- `grafana.external.url`: use your Grafana's URL, e.g. 
`https://grafana.example.com`
 
 Here is the example:
 
@@ -280,8 +280,8 @@ helm repo add devlake 
https://apache.github.io/incubator-devlake-helm-chart
 helm repo update
 ENCRYPTION_SECRET=$(openssl rand -base64 2000 | tr -dc 'A-Z' | fold -w 128 | 
head -n 1)
 helm install devlake devlake/devlake \
-  --set grafana.useExternal=true \
-  --set grafana.externalUrl=https://grafana.example.com
+  --set grafana.enabled=false \
+  --set grafana.external.url=https://grafana.example.com
   --set lake.encryptionSecret.secret=$ENCRYPTION_SECRET
 
 ```

Reply via email to