Skip to content

Add support for syncing to Supabase projects #1013

Description

@bnjns

Is your feature request related to a problem?

We have several Supabase projects and want to manage their edge function secrets centrally rather than per-project, as this requires people to have elevated access to Supabase and people have to set/manage them manually.

Describe the solution you'd like

A secret sync for Supabase, following the same pattern as the existing Vercel/Render/Railway syncs. Supabase's Management API exposes edge function secrets at GET/POST/DELETE /v1/projects/{ref}/secrets, authenticated with a personal access token. A sync would need a project ref plus that token, and could push/prune the same way the other syncs handle deletion.

Describe alternatives you've considered

  • Fetching secrets from Phase directly at runtime inside the edge functions (e.g. via fetch using a service token or the node SDK). Works, but adds a network dependency and cold-start latency to every function, and means we'd have to provision a service account for each project.

Additional context

We're evaluating Phase against Infisical for our secrets and config management, and this is the only meaningful gap we've found.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions