Files
route-commerce/supabase/migrations/.archived/209_authjs_auto_create_admin.sql
T
openclaw 916ad39176
Deploy to route.crispygoat.com / deploy (push) Failing after 3m1s
feat(storage): MinIO object storage, Neon Auth, Supabase removal
- Add MinIO/S3-compatible storage client (src/lib/storage.ts) with uploadObject,
  deleteObject, presigned URL helpers, and BUCKETS constant
- Wire product images, brand logos, and water log photos to MinIO via the
  new storage client
- Migrate forgot-password to Neon Auth (remove Supabase /auth/v1/recover call)
- Migrate send-scheduled cron to direct Postgres + Resend (remove Supabase Edge
  Function proxy)
- Add logoUrl to email types (OrderReceipt, Welcome, PasswordReset) and pass
  brand_settings.logo_url from all call sites
- Update email templates to use dynamic logoUrl instead of hardcoded Supabase
  bucket URLs
- Remove hardcoded Supabase URLs from TuxedoVideoHero, TuxedoAboutPage,
  TimeTrackingFieldClient; use brand_settings props + local public/ fallback
- Download brand logos (3) and tuxedo-hero.mp4 (36MB) from Supabase bucket to
  public/ for local development
- Add MinIO env vars to .env.example (endpoint, access key, secret, buckets)
- Fix TimeTrackingFieldClient to destructure logoUrl and brandAccent props
- Fix admin/users.ts logoUrl type (null → undefined for optional string)
- Remove stale sb- cookie from wholesale-auth
- Migrate tuxedo/about page to remove supabase import and use pool query for
  wholesale_settings lookup
2026-06-09 12:23:37 -06:00

96 lines
2.9 KiB
PL/PgSQL

-- 209_authjs_auto_create_admin.sql
-- Auto-create a platform_admin row when a new user signs in via Auth.js.
--
-- Called from the `signIn` event in `src/lib/auth.ts`. The RPC is
-- idempotent (ON CONFLICT DO NOTHING) so repeat sign-ins are no-ops.
-- Defensive: ensure can_manage_settings column exists. It was likely
-- added via the Supabase dashboard (it's referenced in the TypeScript
-- `AdminUser` type at `src/lib/admin-permissions-types.ts` but not in
-- any tracked migration). ADD COLUMN IF NOT EXISTS is safe to re-run.
ALTER TABLE admin_users
ADD COLUMN IF NOT EXISTS can_manage_settings BOOLEAN NOT NULL DEFAULT false;
-- Defensive: ensure admin_users.user_id has a unique constraint so the
-- `ON CONFLICT (user_id)` below resolves. The table was created via the
-- Supabase dashboard — we can't be sure the dashboard created a UNIQUE
-- index on user_id. If the constraint is missing, the ON CONFLICT
-- clause will fail the whole "Apply migrations" step on the deploy
-- runner. Skip silently if a matching unique/primary constraint already
-- exists, otherwise add one (cleaning up any duplicate rows first so
-- the ADD CONSTRAINT doesn't fail).
DO $$
BEGIN
IF NOT EXISTS (
SELECT 1
FROM pg_constraint
WHERE conrelid = 'public.admin_users'::regclass
AND contype IN ('u', 'p') -- unique or primary key
AND pg_get_constraintdef(oid) ILIKE '%(user_id)%'
) THEN
-- Shouldn't happen in practice (this RPC is the only writer for new
-- rows), but guard against duplicate user_id values that would
-- block the unique constraint from being created.
DELETE FROM admin_users a
USING admin_users b
WHERE a.user_id = b.user_id
AND a.ctid > b.ctid;
ALTER TABLE admin_users
ADD CONSTRAINT admin_users_user_id_key UNIQUE (user_id);
END IF;
END $$;
-- SECURITY DEFINER RPC: upsert a platform_admin row for the given
-- Auth.js user id.
--
-- Bypasses RLS on admin_users (which is enabled — see
-- 109_enable_rls_critical.sql:21). Runs with the function owner's
-- privileges so the auto-create on first sign-in can always succeed.
CREATE OR REPLACE FUNCTION upsert_admin_user_for_authjs(p_user_id UUID)
RETURNS SETOF admin_users
LANGUAGE plpgsql
SECURITY DEFINER
SET search_path = public
AS $$
BEGIN
RETURN QUERY
INSERT INTO admin_users (
user_id,
role,
active,
must_change_password,
can_manage_products,
can_manage_stops,
can_manage_orders,
can_manage_pickup,
can_manage_messages,
can_manage_refunds,
can_manage_users,
can_manage_water_log,
can_manage_reports,
can_manage_settings
)
VALUES (
p_user_id,
'platform_admin',
true,
false,
true,
true,
true,
true,
true,
true,
true,
true,
true,
true
)
ON CONFLICT (user_id) DO NOTHING
RETURNING *;
END;
$$;
-- Reload PostgREST schema cache so the new RPC is immediately callable.
NOTIFY pgrst, 'reload schema';