Documentation
Secrets and guided setup
Miglify detects required Secrets and guides secure configuration for the destination according to the selected workflow.
What Miglify can detect
- Names of Secrets referenced by Edge Functions.
- Which Secrets already exist at the destination.
- Which Secrets still need to be configured before deployment.
How configuration works
Miglify completes Secret configuration through the available automatic or guided workflow, depending on the selected migration workflow and the Supabase authorization you provide.
When a value is requested
When a required value cannot be transferred automatically, Miglify asks you to provide it securely before the dependent Edge Function is considered ready.
Guided setup
You can also configure destination Secrets directly in Supabase and confirm readiness in Miglify.
Security notes
Important
- Secret values are not displayed after saving.
- Secret values are not exposed in customer-facing logs or migration summaries.
- Supabase authorization tokens are used for the requested operation only and are not retained for reuse.
- Guided configuration remains available for any Secret.
Best practices
- Rotate Secrets after testing.
- Use least-privilege values scoped to the destination project.
- Never send Secret values through support messages.
Related docs
Ready to start?
Create a migration when your source, destination, and required credentials are ready.