Sync secrets with rotation between vault and edge functinos
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start by locating the CLI code that manages Vault secrets and Edge Function secrets; no specific files or tests are named in the issue. Clarify the synchronization and rotation behavior, then define completion as Vault updates being propagated to Edge Functions with the required security guarantees and any agreed versioning behavior.
Written by the indexing model from the issue text.
Description
Description:
It would be highly beneficial to enable seamless syncing between Vault secrets and Edge Function secrets. Currently, secrets stored in Vault cannot be automatically propagated to Edge Functions, which limits the integration of Vault as part of the ecosystem.
Use Case:
For example, if I have an Edge Function that should only be callable by the database, having a synced secret would allow me to enforce this securely and reliably without manual updates. This ensures consistency and reduces the risk of secret mismatches across services.
Proposed Enhancement:
- Allow automatic syncing of Vault secrets to Edge Functions.
- Ensure updates in Vault are reflected in Edge Functions in near real-time.
- (optional) Support versioning or rotation to maintain security best practices.
Benefit:
- Streamlines secret management across the ecosystem.
- Enhances security by centralizing secrets in Vault while allowing Edge Functions to use them seamlessly.
- Reduces manual overhead and potential human error in secret distribution.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 523
- Avg merge
- 21h 20m
- Merged PRs (30d)
- 258
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from supabase/cli
-
🐛 Bug supabase/cli
Difficulty 4/5 3-5 days Newbie friendliness 58/100
-
🐛 Bug supabase/cli
-
🐛 Bug supabase/cli
-
🐛 Bug supabase/cli
-
🐛 Bug supabase/cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·