mirror of
https://github.com/supabase/supabase.git
synced 2026-11-06 20:38:12 +08:00
8047d93e3c
## Problem The pipeline wizard from #51776 allows users to continue without valid destination credentials. This is the next slice of #49243. ## Solution - Validate connection fields for all four destinations using the existing schemas and helpers. - Validate the destination on **Continue** and advance to Data on success. Show field errors and connection failures inline; pause for warnings before continuing. - Require a new check after connection settings change and block browser-history shortcuts past an unverified connection. | Errored Test | Success Test | | --- | --- | | <img width="1532" height="2062" alt="CleanShot 2026-10-16 at 12 19 51@2x" src="https://github.com/user-attachments/assets/a40a6c01-ee89-4601-b5d7-6ffc85071dc7" /> | <img width="1500" height="1950" alt="CleanShot 2026-10-16 at 12 18 33@2x" src="https://github.com/user-attachments/assets/c50c1ad4-256b-44b5-bd06-ec0685aae759" /> | The screenshots show earlier test states; successful checks now advance directly to Data. Data validation and pipeline creation remain for later slices. **Start pipeline** stays disabled. ## Review instructions 1. Open the [Pipelines preview](https://studio-staging-git-dnywh-featpipeline-connectio-eb9566-supabase.vercel.app/dashboard/project/_/database/pipelines), select a test project and enable **Pipeline creation wizard**. Open the [wizard preview](https://studio-staging-git-dnywh-featpipeline-connectio-eb9566-supabase.vercel.app/dashboard/project/_/database/pipelines/new) for that project. 2. Choose a destination and click **Continue** with empty or invalid fields. Check the errors, then enter valid credentials and retry. A failed check keeps your values. A failed result stays visible while editing, until retry or destination change. Changed settings still require a fresh check. A successful check opens Data automatically; warnings remain for review before continuing. 3. Continue to Data, return to Connection and change a credential or advanced connection setting. Check that browser **Forward** cannot skip the new check, then click **Continue** to validate again.