alembic-ini-dev-db-url-triggers-secret-scanner
Placing a dev database URL (e.g. postgresql://user:pass@localhost/db) directly in alembic.ini causes the pre-commit secret scanner to block the commit. The correct pattern is to leave the sqlalchemy.url field empty in alembic.ini and rely entirely on the RSAME_DATABASE_URL environment variable, which alembic env.py already reads. This applies to all Alembic-managed Python projects on this host.
Related
- alembic-ini-db-url-blocks-commit-use-env-var
- docker
- openclaw
- r-same-wave-0-scaffold-complete
- notebooklm
- alembic-ini-hardcoded-db-url-triggers-secret-scanner
- jwt-refresh-token-rotation-must-be-atomic
- alembic-ini-db-url-secret-scanner-catches-plaintext
- git-secret-scanner-blocks-alembic-ini-db-url
- alembic-ini-database-url-triggers-secret-scanner
- alembic-ini-must-have-empty-db-url-use-env-var
- secret-scanner-flags-test-passwords-use-labeled-constants
- alembic-ini-hardcoded-url-triggers-secret-scanner
- alembic-ini-db-url-triggers-secret-scanner-on-commit
- alembic-ini-db-url-triggers-secret-scanner