-- analytics_ro_role.sql — dedicated read-only LOGIN role for the analytics MCP server.
--
-- Sibling of dashboard_ro_role.sql, but for the decision & analytics team's MCP
-- server (analytics_mcp_rev.py) rather than the dashboard bridge. A separate role
-- keeps the two access paths independently revocable and lets us apply tighter,
-- human-ad-hoc-query guards (statement_timeout, idle-txn timeout) without touching
-- the dashboard bridge's credential.
--
-- Run as the postgres SUPERUSER (CREATE ROLE), NOT via run_migrations.py (which
-- connects as the app role and may lack CREATEROLE). Apply with
-- scripts/bootstrap_analytics_ro.sh, which supplies the password as the psql
-- variable :ro_pw from a host-only 0600 file — so no secret lives in this repo.
--
-- It grants exactly the read surface the MCP server needs:
--   * SELECT on reporting.* and tracksolid.* (tables + views)
--   * SELECT on the reporting.v_trips MATERIALIZED VIEW — matviews are NOT
--     covered by GRANT ... ON ALL TABLES, so it must be named explicitly
--   * EXECUTE on the reporting.fn_* functions (so analysts can SELECT reporting.fn_...)
--   * DEFAULT PRIVILEGES so future objects created by the migration role are
--     auto-readable (no re-grant when we add views)
-- Read-only: no INSERT/UPDATE/DELETE and not the matview owner, so analytics_ro
-- can never write or REFRESH. Idempotent -> safe to re-apply (also rotates pw).

\set ON_ERROR_STOP on

DO $role$
BEGIN
  IF NOT EXISTS (SELECT 1 FROM pg_roles WHERE rolname = 'analytics_ro') THEN
    CREATE ROLE analytics_ro LOGIN NOSUPERUSER NOCREATEDB NOCREATEROLE;
  END IF;
END $role$;

ALTER ROLE analytics_ro WITH LOGIN PASSWORD :'ro_pw';

GRANT CONNECT ON DATABASE tracksolid_db TO analytics_ro;
GRANT USAGE ON SCHEMA reporting, tracksolid TO analytics_ro;

GRANT SELECT  ON ALL TABLES    IN SCHEMA reporting  TO analytics_ro;  -- tables + views
GRANT SELECT  ON ALL TABLES    IN SCHEMA tracksolid TO analytics_ro;  -- tables + views
GRANT SELECT  ON reporting.v_trips TO analytics_ro;                   -- MATERIALIZED VIEW (not in ALL TABLES)
GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA reporting  TO analytics_ro;

-- "dynamic": future objects created by the migration role (tracksolid_owner)
-- are auto-granted. NOTE: matviews are still never covered — a new matview needs
-- its own explicit GRANT SELECT (as above for v_trips).
ALTER DEFAULT PRIVILEGES FOR ROLE tracksolid_owner IN SCHEMA reporting  GRANT SELECT  ON TABLES    TO analytics_ro;
ALTER DEFAULT PRIVILEGES FOR ROLE tracksolid_owner IN SCHEMA tracksolid GRANT SELECT  ON TABLES    TO analytics_ro;
ALTER DEFAULT PRIVILEGES FOR ROLE tracksolid_owner IN SCHEMA reporting  GRANT EXECUTE ON FUNCTIONS TO analytics_ro;

-- Extra hardening over dashboard_ro: this role serves ad-hoc HUMAN queries via the
-- MCP server, so pin read-only at the role level and cap runaway work. These are
-- belt-and-braces alongside the read-only txn the server itself uses.
ALTER ROLE analytics_ro SET default_transaction_read_only = on;
ALTER ROLE analytics_ro SET statement_timeout = '30s';
ALTER ROLE analytics_ro SET idle_in_transaction_session_timeout = '60s';
