📈(helm) add separate namespaces for each environment

I have set up distinct namespaces for each environment. You can now push events to the development namespace without affecting production data. Please note that these keys are not 'secret'. They will also be configured in the browser SDK, which is inherently insecure. The documentation does not specify a secure storage method for these keys.
numerique-gouv · Aug 5, 2024 · 100d79c · 100d79c
1 parent 9e92b81
commit 100d79c
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 1 deletion.
diff --git a/src/helm/env.d/dev/values.meet.yaml.gotmpl b/src/helm/env.d/dev/values.meet.yaml.gotmpl
@@ -46,7 +46,7 @@ backend:
     {{- end }}
     {{- end }}
     LIVEKIT_API_URL: https://livekit.127.0.0.1.nip.io/
-
+    ANALYTICS_KEY: xwhoIMCZ8PBRjQ2t
 
   migrate:
     command:

diff --git a/src/helm/env.d/production/values.meet.yaml.gotmpl b/src/helm/env.d/production/values.meet.yaml.gotmpl
@@ -93,6 +93,7 @@ backend:
         name: backend
         key: LIVEKIT_API_KEY
     LIVEKIT_API_URL: https://livekit-preprod.beta.numerique.gouv.fr
+    ANALYTICS_KEY: mwuxTKi8o2xzWH54
 
   createsuperuser:
     command:

diff --git a/src/helm/env.d/staging/values.meet.yaml.gotmpl b/src/helm/env.d/staging/values.meet.yaml.gotmpl
@@ -93,6 +93,7 @@ backend:
         name: backend
         key: LIVEKIT_API_KEY
     LIVEKIT_API_URL: https://livekit-preprod.beta.numerique.gouv.fr
+    ANALYTICS_KEY: Roi1k6IAc2DEqHB0
 
   createsuperuser:
     command: