From 87b4ec2c5eae708ffd36f9bcda2498890aaddcbe Mon Sep 17 00:00:00 2001 From: nfebe Date: Tue, 3 Feb 2026 20:18:31 +0100 Subject: [PATCH] fix(domains): Remove redundant legacy domain migration Remove frontend code that added legacy domain before adding new domain. The backend already handles legacy domain migration in addDomain API, so the frontend migration was causing duplicates when add failed and user retried. Signed-off-by: nfebe --- src/views/DeploymentDetailView.vue | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/src/views/DeploymentDetailView.vue b/src/views/DeploymentDetailView.vue index 66c79c3..dbdd9c9 100644 --- a/src/views/DeploymentDetailView.vue +++ b/src/views/DeploymentDetailView.vue @@ -1798,23 +1798,8 @@ const fetchProxyStatus = async () => { const handleAddDomain = async (newDomain: any) => { if (!deployment.value?.metadata) return; - const currentDomain = deployment.value.metadata.networking?.domain; - const currentPort = deployment.value.metadata.networking?.container_port || 80; - const currentSSL = deployment.value.metadata.ssl || { enabled: false, auto_cert: false }; - addingDomain.value = true; try { - // First, convert existing legacy domain to a domain config - if (currentDomain) { - await deploymentsApi.addDomain(route.params.name as string, { - service: deployment.value.metadata.name || (route.params.name as string), - container_port: currentPort, - domain: currentDomain, - ssl: currentSSL, - }); - } - - // Then add the new domain await deploymentsApi.addDomain(route.params.name as string, { service: newDomain.service || deployment.value.metadata.name || (route.params.name as string), container_port: newDomain.container_port || 80,