mirror of https://github.com/supabase/supabase.git synced 2026-06-22 07:22:07 +08:00

Files

Tomás Pozo e3be344f5c fix(examples): read new API keys directly from parsed SUPABASE_SECRET_KEYS (#46604 )

## Problem

Edge Function examples that use the new publishable/secret API keys read
them with a double lookup:

```ts
const SUPABASE_SECRET_KEYS = JSON.parse(Deno.env.get('SUPABASE_SECRET_KEYS')!)
const secretKey = Deno.env.get(SUPABASE_SECRET_KEYS['default']) // ❌ returns undefined
```

`SUPABASE_SECRET_KEYS` / `SUPABASE_PUBLISHABLE_KEYS` are a JSON object
that maps a key name to the **actual key value** (e.g.
`{"default":"sb_secret_..."}`), confirmed by:
- the self-hosted injection in `docker/docker-compose.yml`
(`SUPABASE_SECRET_KEYS: "{\"default\":\"${SUPABASE_SECRET_KEY:-}\"}"`)
- the `@supabase/server` SDK README

So `SUPABASE_SECRET_KEYS['default']` is already the key. Wrapping it in
another `Deno.env.get(...)` looks up an env var named `sb_secret_...`,
which doesn't exist, so the value is `undefined` and the examples fail
at runtime.

## Fix

Unwrap the outer `Deno.env.get(...)` so the key is read directly:

```ts
const SUPABASE_SECRET_KEYS = JSON.parse(Deno.env.get('SUPABASE_SECRET_KEYS')!)
const secretKey = SUPABASE_SECRET_KEYS['default'] // ✅
```

Applied across 23 files (example functions, the
`examples/prompts/edge-functions.md` codegen guidance, and two docs
guides). The correct `JSON.parse(Deno.env.get('SUPABASE_SECRET_KEYS')!)`
declaration line is untouched. The generated `apps/docs/examples/` copy
regenerates from `examples/` at build time.

## Notes

- Docs context:
[#46600](https://github.com/supabase/supabase/pull/46600), which
documents the same key model.
- Follow-up (not in this PR): a few examples send the secret key on the
`Authorization: Bearer` header, which the new keys reject. Worth a
separate audit.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Clarified examples and guides for correctly reading parsed Supabase
secret and publishable key maps.

* **Examples**
* Standardized credential usage across Edge Functions and samples so
Supabase clients consistently receive keys from the parsed key maps
rather than indirect lookups.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>

2026-06-03 11:05:20 -05:00

supabase

fix(examples): read new API keys directly from parsed SUPABASE_SECRET_KEYS (#46604 )

2026-06-03 11:05:20 -05:00

README.md

docs: Examples Key changes (#45170 )

2026-05-04 12:58:16 +02:00

README.md

AI Inference in Supabase Edge Functions

Since Supabase Edge Runtime v1.36.0 you can run the gte-small model natively within Supabase Edge Functions without any external dependencies! This allows you to easily generate text embeddings without calling any external APIs!

Semantic Search with pgvector and Supabase Edge Functions

This demo consists of three parts:

A generate-embedding database webhook edge function which generates embeddings when a content row is added (or updated) in the public.embeddings table.
A query_embeddings Postgres function which allows us to perform similarity search from an egde function via Remote Procedure Call (RPC).
A search edge function which generates the embedding for the search term, performs the similarity search via RPC function call, and returns the result.

Deploy

Link your project: supabase link
Deploy Edge Functions: supabase functions deploy
Update project config to enable webhooks: supabase config push
Navigate to the database-webhook migration file and insert your generate-embedding function details.
Push up the database schema supabase db push

Run

Run a search via curl POST request:

curl -i --location --request POST 'https://<PROJECT-REF>.supabase.co/functions/v1/search' \
    --header 'apikey: <SUPABASE_PUBLISHABLE_KEY>' \
    --header 'Content-Type: application/json' \
    --data '{"search":"vehicles"}'