Provision fuzesocial DB + fuzesocial_app role on shared Postgres

[izzywdev]

@claude

Request

Please ensure the following are provisioned on the shared FuzeInfra Postgres cluster (Contabo k3s, fuzeinfra-postgres.fuzeinfra.svc.cluster.local:5432):

Resource	Details
Database	fuzesocial
Role	fuzesocial_app
Permissions	CONNECT on fuzesocial, CREATE/SELECT/INSERT/UPDATE/DELETE on all tables in public schema, USAGE/SELECT on all sequences

Context

FuzeSocial (repo: izzywdev/FuzeSocial) is a new consumer of the shared FuzeInfra Postgres. Per the consumer onboarding guidelines, FuzeSocial must NOT hold the superuser credentials — DB + role provisioning is FuzeInfra's responsibility.

The FuzeSocial Helm chart (deploy/helm/fuzesocial/) has a pre-sync bootstrap Job that connects as fuzesocial_app (via DB_PASSWORD SealedSecret) to apply schema.sql and seed.sql. It requires the DB and role to already exist at sync time.

The password for fuzesocial_app should be delivered as a GitHub Actions secret FUZESOCIAL_DB_PASSWORD on the izzywdev/FuzeSocial repo (never in this issue).

Acceptance

• fuzesocial database exists on the shared Postgres
• fuzesocial_app role exists with the above permissions
• FUZESOCIAL_DB_PASSWORD GH Actions secret is set on izzywdev/FuzeSocial
• FuzeSocial bootstrap Job (kubectl -n fuzesocial logs job/fuzesocial-db-bootstrap) completes successfully

STATE: pending — awaiting provisioning

[claude]

Claude finished @izzywdev's task in 0s —— View job

---

I'll analyze this and get back to you.

[izzywdev]

@claude — your previous run finished in 0s without doing any work. Please check first whether fuzesocial DB + fuzesocial_app role already exist on the shared Postgres (check helm/fuzeinfra/values-contabo.yaml serviceDatabases block). If already provisioned, close this issue. If not, implement the provisioning per the original request.

[izzywdev]

⚠️ Claude responder did not run to completion

The responder errored before finishing your request, so no changes were made and no branch was created.

• Reason: Anthropic API rejected preflight (HTTP 400): Your credit balance is too low to access the Anthropic API. Please go to Plans & Billing to upgrade or purchase credits.
• Run log: https://github.com/izzywdev/FuzeInfra/actions/runs/29936767097

This notice is automated and will not retry on its own — the responder stops after one failure and waits. If this looks like an API-side problem (key revoked / out of credits / model or 1M-context beta not entitled / Anthropic outage), an operator should check the ANTHROPIC_API_KEY secret and fund/repair the Anthropic account first, then re-trigger by posting a new comment mentioning the responder.

[izzywdev]

Not yet done. No fuzesocial entry in serviceDatabases in values-contabo.yaml (checked 2026-08-02). The provisioning pattern is established (mendys, fuzesales, fuzecontact, fuzeservice are all there). To implement: add a fuzesocial entry to serviceDatabases in values-contabo.yaml with its passwordSecret, and create a fuzesocial-db-credentials SealedSecret.