cameleer/cameleer-saas
2
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

fix: use configured credentials for tenant schema cleanup
All checks were successful
CI / build (push) Successful in 1m9s
Details
CI / docker (push) Successful in 39s
Details

Browse Source 
Same hardcoded dev credentials bug as InfrastructureService —
TenantDataCleanupService.dropPostgresSchema() used "cameleer"/"cameleer_dev"
instead of the provisioning properties, causing schema DROP to fail on
production installs during tenant deletion.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
hsiegeln
2026-04-14 23:11:16 +02:00
parent 03fb414981
commit bc46af5cea
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
src/main/java/net/siegeln/cameleer/saas/provisioning/TenantDataCleanupService.java
View File

@@ -44,7 +44,7 @@ public class TenantDataCleanupService {
return; return;
} }
try (Connection conn = DriverManager.getConnection(url, "cameleer", "cameleer_dev"); try (Connection conn = DriverManager.getConnection(url, props.datasourceUsername(), props.datasourcePassword());
Statement stmt = conn.createStatement()) { Statement stmt = conn.createStatement()) {
stmt.execute("DROP SCHEMA IF EXISTS \"" + schema + "\" CASCADE"); stmt.execute("DROP SCHEMA IF EXISTS \"" + schema + "\" CASCADE");
log.info("Dropped PostgreSQL schema: {}", schema); log.info("Dropped PostgreSQL schema: {}", schema);