From 43ed86903dfd23821dc2c472710aaec7d3766cf8 Mon Sep 17 00:00:00 2001 From: aarroyo Date: Sat, 25 Jul 2026 19:39:25 -0500 Subject: [PATCH] =?UTF-8?q?chore(e2e):=20renombrar=20el=20cl=C3=BAster=20l?= =?UTF-8?q?ocal=20a=20evolith-ums-cluster?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Alinea el nombre del clúster kind con la identidad del satélite Evolith (evolith.yaml → metadata.name: evolith-ums): beyondnet-cluster-ums → evolith-ums-cluster (contexto kubectl kind-evolith-ums-cluster). Solo afecta al arnés E2E robosoft (comentarios/README/comandos kubectl), sin lógica. Co-Authored-By: Claude Opus 4.8 --- src/tests/e2e-functional/robosoft/README.md | 4 ++-- src/tests/e2e-functional/robosoft/api/README-api.md | 2 +- src/tests/e2e-functional/robosoft/api/playwright.config.ts | 2 +- src/tests/e2e-functional/robosoft/robosoft.py | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/tests/e2e-functional/robosoft/README.md b/src/tests/e2e-functional/robosoft/README.md index 7a0aa464..e8652d30 100644 --- a/src/tests/e2e-functional/robosoft/README.md +++ b/src/tests/e2e-functional/robosoft/README.md @@ -50,8 +50,8 @@ Cada módulo de contexto expone tres símbolos: ### 1) Backend vivo en kind ```bash -# Port-forward al backend desplegado en el clúster local beyondnet-cluster-ums: -kubectl --context kind-beyondnet-cluster-ums -n ums \ +# Port-forward al backend desplegado en el clúster local evolith-ums-cluster: +kubectl --context kind-evolith-ums-cluster -n ums \ port-forward svc/ums-backend 18080:80 & # Verifica salud: curl -s -o /dev/null -w "%{http_code}\n" http://localhost:18080/health # -> 200 diff --git a/src/tests/e2e-functional/robosoft/api/README-api.md b/src/tests/e2e-functional/robosoft/api/README-api.md index 405fed50..5169614d 100644 --- a/src/tests/e2e-functional/robosoft/api/README-api.md +++ b/src/tests/e2e-functional/robosoft/api/README-api.md @@ -41,7 +41,7 @@ En `Development` el backend expone dos caminos, ambos usados por este arnés: ## Cómo correrlo -Requiere el backend vivo (health 200). El clúster local es `beyondnet-cluster-ums`. +Requiere el backend vivo (health 200). El clúster local es `evolith-ums-cluster`. ```bash # Directo (solo carril B): diff --git a/src/tests/e2e-functional/robosoft/api/playwright.config.ts b/src/tests/e2e-functional/robosoft/api/playwright.config.ts index 51fb3a9a..2a0bfb5c 100644 --- a/src/tests/e2e-functional/robosoft/api/playwright.config.ts +++ b/src/tests/e2e-functional/robosoft/api/playwright.config.ts @@ -6,7 +6,7 @@ // API REST y aseverar reglas de negocio, auto-aprovisionando su propia data. // // `E2E_BASE_URL` apunta al despliegue ya levantado (Ingress del clúster kind -// `beyondnet-cluster-ums`, por defecto http://localhost:8080). Este arnés NO levanta servidores. +// `evolith-ums-cluster`, por defecto http://localhost:8080). Este arnés NO levanta servidores. import { defineConfig } from '@playwright/test'; const baseURL = process.env.E2E_BASE_URL ?? 'http://localhost:8080'; diff --git a/src/tests/e2e-functional/robosoft/robosoft.py b/src/tests/e2e-functional/robosoft/robosoft.py index f9bcff5b..8fc7f6e2 100644 --- a/src/tests/e2e-functional/robosoft/robosoft.py +++ b/src/tests/e2e-functional/robosoft/robosoft.py @@ -8,7 +8,7 @@ Uso: # 1) Port-forward al backend en kind (en otra terminal o en background): - kubectl --context kind-beyondnet-cluster-ums -n ums \\ + kubectl --context kind-evolith-ums-cluster -n ums \\ port-forward svc/ums-backend 18080:80 & # 2) Correr los 3 contextos implementados: