chore: re-trigger ai-credits CI with corrected TEST_DATABASE_URL password
All checks were successful
build-and-release / build (developers) (push) Successful in 9s
build-and-release / build (companies) (push) Successful in 12s
build-and-release / build (cron) (push) Successful in 16s
build-and-release / build (catering-services) (push) Successful in 19s
build-and-release / build (employees) (push) Successful in 16s
build-and-release / build (fitness-trainers) (push) Successful in 8s
build-and-release / build (gateway) (push) Successful in 7s
build-and-release / build (customers) (push) Successful in 20s
build-and-release / build (graphic-designers) (push) Successful in 6s
build-and-release / build (jobs) (push) Successful in 5s
build-and-release / build (makeup-artists) (push) Successful in 6s
build-and-release / build (job-seekers) (push) Successful in 11s
build-and-release / build (photographers) (push) Successful in 5s
build-and-release / build (payments) (push) Successful in 11s
build-and-release / build (social-media-managers) (push) Successful in 5s
build-and-release / build (ugc-content-creators) (push) Successful in 5s
build-and-release / build (video-editors) (push) Successful in 6s
build-and-release / build (tutors) (push) Successful in 11s
build-and-release / build (users) (push) Successful in 11s
backend-integration-tests / ai-credits (push) Successful in 5s

Discovered POSTGRES_PASSWORD env var on the postgres pod itself is
stale/unused for network auth - pg_hba.conf only trusts it for local
socket connections (no password check at all there). The real
scram-sha-256 password the live app pods actually use over the network
lives in the nxtgauge-backend-rust-secrets K8s secret's DATABASE_URL
key. Used that instead.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Ashwin Kumar Sivakumar 2026-08-13 20:14:04 +05:30
parent c307ef1ba4
commit 786ad41bd8

Diff content is not available