- Shipped
- October 18, 2026 at 10:15 PM UTC
- Author
- Kamo
- Commit
- 5a261df
The YugabyteDB application password was exposed (com.zaxxer.hikari DEBUG in ten services' logs, and securityservice's committed diagnose-output.txt), so it was rotated on 2026-10-18 with zero downtime: a new LOGIN role, an INHERIT member of kamo_app with `SET role = 'kamo_app'`, so every session still runs as kamo_app with the same privileges and ownership. All 40 consumers were rolled onto it one at a time, then kamo_app was made NOLOGIN with no password. 03-app-role.sql now takes app_user and app_password and keeps kamo_app NOLOGIN. It refuses app_user=kamo_app, because re-running the old version would have put LOGIN back on kamo_app. The README describes the model and the rotation procedure, and SECRETS.md lists the DB login Secret and its copies. No secret values are included.