postgres.go extends Core with managed-Postgres methods over the Database CR, mirroring Render's /v1/postgres API. Same one-Core design: REST and GraphQL call these; the connection-info method is the one place the DB password is surfaced (to an authenticated caller only), read from CNPG's generated S
source not stored for this graph (policy: none)
nothing calls this directly
no outgoing calls
no test coverage detected