mirror of
https://github.com/garrytan/gstack.git
synced 2026-11-22 16:11:34 +01:00
Telemetry backend only accepts writes through its own endpoint, and tests stop sending to it (GST-3234) (#4537)
The telemetry backend now takes writes only through its validated endpoint, signed-in Supabase users can read or write nothing, and gstack's tests can no longer send telemetry to the live project. Why: a signed-in prober read two views on 2026-11-19, probes wrote about 2,000 junk rows through the open insert policy, and 41% of all skill-run rows were test-suite traffic. Nothing changes for users until the migrations and edge functions are deployed; the deploy order is under Deploy. Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> Review-Finding: p1/red-team#1 reader=red-team Review-Finding: supabase/migrations/008_close_anon_writes.sql:9:published-number reader=core Review-Finding: p2/outside-voice#3 reader=outside-voice
This commit is contained in:
1 parent
dab7549451
commit
12cc21872d
15 files changed
+704
-270
No files matched your search
+5
-2
@@ -26,8 +26,11 @@ no, and `gstack-config set telemetry off` turns it off at any time.
|
||||
- **Where it goes:** [Supabase](https://supabase.com) (an open-source Firebase
|
||||
alternative). The schema is in [`supabase/migrations/`](../supabase/migrations/),
|
||||
so you can verify what's collected. The publishable key in the repo is a
|
||||
public key; row-level security denies direct access, and edge functions
|
||||
enforce schema checks, event allowlists and field length limits.
|
||||
public key that can neither read nor write those tables; every write goes
|
||||
through edge functions that enforce schema checks, event allowlists and
|
||||
field length limits. gstack never uses Supabase sign-in, and signed-in users
|
||||
are denied everything too. gstack's own test suite never sends telemetry
|
||||
to the live project.
|
||||
|
||||
**Update check (on by default, regardless of telemetry).** Every interactive
|
||||
skill start runs `gstack-update-check`. When its cache is stale (60 minutes after an
|
||||
|
||||
Reference in new issue
Block a user