Maximilian Stubhan
b87c8ad64c
The database moved to a container of our own; the platform is gone. This takes out what was left of it — and, where the leftovers were load bearing, moves rather than deletes. Moved, not deleted: supabase/migrations/ -> db/migrations/ the schema's source of truth supabase/build-org.ts -> scripts/build-org.ts lib/supabase/types.ts -> lib/types.ts 52 import sites repointed The bookkeeping needed care. It lived in `supabase_migrations.schema_migrations`, and simply renaming the schema would have left the runner facing an empty table: it would have called all 67 migrations pending and replayed them against a database that is long since current. So the runner now creates `migrationen.schema_migrations` and, once, copies the old rows across — guarded so a second run does nothing and a fresh database skips it entirely. Only then does migration 20260907100000 drop the old schema. Deleted: the CLI config, the seed, the historical schema/function dumps (nothing read them), scripts/umzug-von-supabase.sh (the move is done), and both Supabase packages plus the CLI. Nothing in the application imported them — the build now succeeds with no environment variables at all, which is the proof. Integration tests: six of them signed in through Supabase Auth and asserted against the anon key and the service role. That model is gone, so the tests were not portable — they are deleted. session-context and employee-status-filter already ran on pg and are untouched; om-reporting is ported to a direct connection because it guards a real risk (the reporting line rule exists twice, once in SQL and once in TypeScript). CI: the integration job started a Supabase stack. It now runs a postgres service, applies deploy/db-init and every migration to an empty database — that was the valuable part, and it still holds — then checks that a second run is a no-op, which is what proves the bookkeeping works. Docs: security-review.md audited a service-role key, a cookie adapter and auth.users, none of which exist. Restating findings about removed components would suggest today's system had been reviewed; it has not. It now records what was removed and says a fresh review is due. data-model.md was already marked obsolete and described the pre-OM schema; azure-migration.md was a plan for a route not taken. Both deleted. Verified: npm ci, typecheck, lint, 445 tests, build — all clean without the packages. Integration tests skip cleanly with no database. Migration SQL and the runner are reviewed but NOT executed: no Docker here, and the old instance no longer resolves. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
60 lines
2.5 KiB
PL/PgSQL
60 lines
2.5 KiB
PL/PgSQL
-- Das RLS-Sicherheitsnetz gehört ins Repository, nicht nur in die Datenbank.
|
|
--
|
|
-- `rls_auto_enable()` und der Ereignis-Trigger `ensure_rls` schalten Row Level
|
|
-- Security bei jeder neu angelegten Tabelle in `public` sofort ein. Sie sind
|
|
-- der Grund, warum eine vergessene Policy nichts preisgibt: ohne RLS wäre eine
|
|
-- neue Tabelle für die Anwendungsrolle offen, mit RLS und ohne Policy ist sie
|
|
-- leer. Ein Fehler wird so zu einer fehlenden Anzeige statt zu einem Leck.
|
|
--
|
|
-- **Gefunden beim Umzug von Supabase auf einen eigenen Container.** Beide
|
|
-- Objekte existierten nur in der laufenden Datenbank — angelegt von Hand, in
|
|
-- keiner Migration. Ein Nachbau aus den Migrationen (die CI tut das bei jedem
|
|
-- Lauf, und ein neuer Server sowieso) hätte das Netz stillschweigend nicht
|
|
-- gehabt: alles funktioniert, nur die nächste neue Tabelle wäre ungeschützt.
|
|
--
|
|
-- Der Text ist der aus der Produktion, unverändert übernommen. Auf einer
|
|
-- Datenbank, die ihn schon hat, ändert diese Migration nichts.
|
|
|
|
create or replace function public.rls_auto_enable()
|
|
returns event_trigger
|
|
language plpgsql
|
|
security definer
|
|
set search_path to 'public', 'pg_temp'
|
|
as $function$
|
|
declare
|
|
cmd record;
|
|
begin
|
|
for cmd in
|
|
select *
|
|
from pg_event_trigger_ddl_commands()
|
|
where command_tag in ('CREATE TABLE', 'CREATE TABLE AS', 'SELECT INTO')
|
|
and object_type in ('table', 'partitioned table')
|
|
loop
|
|
if cmd.schema_name is not null and cmd.schema_name in ('public') then
|
|
begin
|
|
execute format('alter table if exists %s enable row level security', cmd.object_identity);
|
|
raise log 'rls_auto_enable: enabled RLS on %', cmd.object_identity;
|
|
exception
|
|
-- Bewusst geschluckt: ein Ereignis-Trigger, der wirft, lässt die
|
|
-- ganze DDL scheitern. Eine Tabelle, an der das Einschalten nicht
|
|
-- klappt, ist ein Fall fürs Protokoll — kein Grund, die Migration
|
|
-- abzubrechen, die sie gerade anlegt.
|
|
when others then
|
|
raise log 'rls_auto_enable: failed to enable RLS on %', cmd.object_identity;
|
|
end;
|
|
else
|
|
raise log 'rls_auto_enable: skip % (Schema %)', cmd.object_identity, cmd.schema_name;
|
|
end if;
|
|
end loop;
|
|
end;
|
|
$function$;
|
|
|
|
-- `create event trigger` kennt kein `if not exists`; deshalb erst weg, dann neu.
|
|
-- Auf einer Datenbank ohne den Trigger ist das `drop` folgenlos.
|
|
drop event trigger if exists ensure_rls;
|
|
|
|
create event trigger ensure_rls
|
|
on ddl_command_end
|
|
when tag in ('CREATE TABLE', 'CREATE TABLE AS', 'SELECT INTO')
|
|
execute function public.rls_auto_enable();
|