5
Upload non-secret environment variables to Edge Function Secrets Management
Source: supabase/supabase#33636 · opened by @Magnuti
Problem
The Edge Function Secrets Management is excellent for secrets, but it is annoying when dealing with non-secret environment variables (for example redirect URLs and public keys), since it is not possible to view the raw value, only the hash. Hiding non-secret environment variables behind a hash is overkill in my opinion.
<img width="800" alt="image" src=" />
Suggestion solution
It would be nice if we were able to upload non-secret environment variables in the Supabase UI, like we can do on GitHub.
<img width="800" alt="image" src=" />
The Edge Function Secrets Management is excellent for secrets, but it is annoying when dealing with non-secret environment variables (for example redirect URLs and public keys), since it is not possible to view the raw value, only the hash. Hiding non-secret environment variables behind a hash is overkill in my opinion.
<img width="800" alt="image" src=" />
Suggestion solution
It would be nice if we were able to upload non-secret environment variables in the Supabase UI, like we can do on GitHub.
<img width="800" alt="image" src=" />
No pledges yet. Be the first to back this.
Comments
Similar requests
Enable Syncing of Vault and Edge Function Secrets
1 vote · 0 comments
Move Away from Using Environment Variables for Secrets
1 vote · 0 comments
OIDC identity tokens for Edge Functions (workload identity federation)
1 vote · 0 comments
[UI/UX Suggestion] Edge Function Editor Height & Mobile Responsiveness Improvements
1 vote · 0 comments
Edge Function runtime events
1 vote · 0 comments
No comments yet.