Superset Dev 2e507214cd fix(telemetry): make SCARF_ANALYTICS opt-out work at runtime ...

The Scarf telemetry pixel was gated only on `process.env.SCARF_ANALYTICS`,
which webpack inlines at build time. On the official Docker image and the
PyPI wheel the frontend is pre-built, so setting `SCARF_ANALYTICS=false`
at container runtime (Helm `extraEnv`, docker/.env, etc.) had no effect —
the documented opt-out simply didn't work for most deployments (#32110).

Expose `SCARF_ANALYTICS` as a backend config read from the environment and
ship it to the client via the bootstrap payload (`FRONTEND_CONF_KEYS`), then
have RightMenu pass it to `<TelemetryPixel enabled>`. The build-time
`process.env` check is kept as a short-circuit for source builds. Default is
unchanged (telemetry on unless explicitly disabled).

Docs (Kubernetes, Docker Compose, FAQ) updated to document the runtime
opt-out; the k8s page previously only covered opting out of image-pull
telemetry, not the pixel.

Fixes #32110

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

# Conflicts:
#	superset-frontend/src/features/home/RightMenu.tsx
#	tests/unit_tests/views/test_base.py

2026-06-26 23:34:15 -07:00

..

configuration

fix(reports): reliability fixes for alert/report execution (#41177)

2026-06-26 12:09:12 -07:00

installation

fix(telemetry): make SCARF_ANALYTICS opt-out work at runtime

2026-06-26 23:34:15 -07:00

security

docs(security): add a secrets register and rotation schedule (#41308)

2026-06-24 16:15:17 -07:00

index.md

docs: bifurcate documentation into user and admin sections (#38196)

2026-02-26 13:29:08 -08:00