From bc46af5cead1b0d177294fde19716f97b9718f2f Mon Sep 17 00:00:00 2001 From: hsiegeln <37154749+hsiegeln@users.noreply.github.com> Date: Tue, 14 Apr 2026 23:11:16 +0200 Subject: [PATCH] fix: use configured credentials for tenant schema cleanup MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- .../cameleer/saas/provisioning/TenantDataCleanupService.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/java/net/siegeln/cameleer/saas/provisioning/TenantDataCleanupService.java b/src/main/java/net/siegeln/cameleer/saas/provisioning/TenantDataCleanupService.java index 49e0fe1..f06dedf 100644 --- a/src/main/java/net/siegeln/cameleer/saas/provisioning/TenantDataCleanupService.java +++ b/src/main/java/net/siegeln/cameleer/saas/provisioning/TenantDataCleanupService.java @@ -44,7 +44,7 @@ public class TenantDataCleanupService { return; } - try (Connection conn = DriverManager.getConnection(url, "cameleer", "cameleer_dev"); + try (Connection conn = DriverManager.getConnection(url, props.datasourceUsername(), props.datasourcePassword()); Statement stmt = conn.createStatement()) { stmt.execute("DROP SCHEMA IF EXISTS \"" + schema + "\" CASCADE"); log.info("Dropped PostgreSQL schema: {}", schema);