SUPABASE_SERVICE_ROLE_KEY is reset locally on "supabase functions serve"

edge functions

When I run

supabase functions serve --env-file ./supabase/.env.local

supabase functions serve --env-file ./supabase/.env.local

locally and then invoke a function via HTTP,

Devo.get('SUPABASE_SERVICE_ROLE_KEY')

Devo.get('SUPABASE_SERVICE_ROLE_KEY')

will reveal a new value every time the "serve" command is executed again.

The JWT payload is always the same, just with a fresh

exp

exp

{
  "iss": "supabase-demo",
  "role": "service_role",
  "exp": 2084610768
}

{
  "iss": "supabase-demo",
  "role": "service_role",
  "exp": 2084610768
}

SUPABASE_SERVICE_ROLE_KEY

SUPABASE_SERVICE_ROLE_KEY

used to be stable. I assume that this has to do with the upcoming/ongoing keys migration, but I according to the migration timeline, the legacy approach should still be functional until late 2026.

Supabase•2mo ago•

8 replies

elektrosteve

SUPABASE_SERVICE_ROLE_KEY is reset locally on "supabase functions serve"

edge functions

When I run

supabase functions serve --env-file ./supabase/.env.local

supabase functions serve --env-file ./supabase/.env.local

locally and then invoke a function via HTTP,

Devo.get('SUPABASE_SERVICE_ROLE_KEY')

Devo.get('SUPABASE_SERVICE_ROLE_KEY')

will reveal a new value every time the "serve" command is executed again.

The JWT payload is always the same, just with a fresh

exp

exp

{
  "iss": "supabase-demo",
  "role": "service_role",
  "exp": 2084610768
}

{
  "iss": "supabase-demo",
  "role": "service_role",
  "exp": 2084610768
}

SUPABASE_SERVICE_ROLE_KEY

SUPABASE_SERVICE_ROLE_KEY

used to be stable. I assume that this has to do with the upcoming/ongoing keys migration, but I according to the migration timeline, the legacy approach should still be functional until late 2026.

SUPABASE_SERVICE_ROLE_KEY is reset locally on "supabase functions serve"

Similar Threads

SUPABASE_SERVICE_ROLE_KEY is reset locally on "supabase functions serve"

Similar Threads

Similar Threads

Similar Threads