Files
windmill/frontend/src/lib/components
Guilhem LemouelandClaude Opus 5 979c055bae fix(frontend): fall back to a direct Supabase connection when the pooler cannot be read
Reading a project's Supavisor config needs the database_pooling_config_read scope, which
an instance's Supabase OAuth app may never have been granted. No retry recovers from
that, and the wizard treated it as fatal: the user was left with an error and no way to
finish connecting a project that was otherwise fine.

resolveSupabaseConnection replaces the bare pooler read everywhere it happened. Asking
for session pooling and failing now yields a direct connection plus the reason, which
supabaseResourceValue already knew how to write. Nothing about the fallback is silent --
direct is IPv6-only, which is the whole reason session pooling is the default -- so the
wizard warns on its review step and the resource drawer says so in its toast.

The row is recorded before credentials are saved, so an origin claiming session pooling
has to be corrected once a direct host is what gets written; the run patches it through
set_datatable_setup rather than leaving the panel to report a mode nothing uses.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-11 11:04:24 +02:00
..
2025-10-30 06:47:26 +00:00
2025-10-28 17:52:04 +00:00
2026-03-05 18:11:40 +01:00
2026-03-05 18:11:40 +01:00
2025-11-04 19:13:09 +00:00
2026-02-11 06:27:21 +00:00
2025-11-29 01:23:47 +00:00
2026-03-05 18:11:40 +01:00
2026-03-05 18:11:40 +01:00