Edge Functions
Miglify detects Edge Functions, evaluates deployment readiness, and deploys supported functions when requirements are met.
Detected Edge Functions
Miglify lists detected Edge Functions with their current deployment readiness so you can see what is ready and what still needs input.
When a function is not yet ready
If a required input is missing — such as source code, a required Secret, or Supabase authorization — Miglify reports the specific requirement instead of deploying the function.
Deployment requirements
- Access to the function source through the selected workflow.
- Destination Supabase project credentials.
- The Supabase authorization required by the deployment workflow.
- Required Secrets configured at the destination.
Completing a function yourself
You can also deploy a function with your own tooling. Miglify continues to track Secret requirements and readiness so the rest of the migration is unaffected.
Secrets required by functions
Configure required Secrets before or after deploy. See the Secrets guide.
Testing after deployment
Invoke the function from your app or a test client to verify behavior and connectivity.
Common issues
- Function source not available to the workflow — provide access or deploy it yourself.
- Missing Secrets — configure them, then retry.
- Invalid or expired Supabase authorization — reauthorize and retry.