chore(infra): eliminar SQL Server del despliegue; estandarizar en PostgreSQL (fase 1)#12
Merged
Merged
Conversation
… en PostgreSQL Fase 1 (despliegue + config; el código de repos/provider queda para fase 2): - Chart infra/local/kubernetes/helm/ums: el `ums` desplegaba SQL Server como BD. Se elimina templates/sqlserver.yaml, se añade templates/postgres.yaml (postgres:15-alpine, svc `postgres`, PVC pgdata) y el api apunta a Postgres (ConnectionStrings Host=postgres;…; Persistence__Provider=PostgreSql + UsePostgreSql*Stores). values.yaml: bloque sqlserver → postgres. - appsettings.Production.json: Provider SqlServer → PostgreSql (era el único entorno con SQL Server activo; Development/UAT/base ya eran Postgres). - infra/accesos_local.md: port-forward svc/sqlserver-lite:1433 → svc/postgres:5432. - infra/plan_es.md: puerto DB interno 5432/1433 → 5432 (PostgreSQL). - Eliminados scripts one-off sin referencias infra/patch_compose.py y patch_di.py. Validado: `helm template` renderiza el chart en Postgres; JSON válido. El código .NET no se toca en esta fase (los repos SqlServer* siguen siendo los relacionales activos de Postgres; su renombrado/limpieza es la fase 2). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Estandariza el despliegue local en PostgreSQL y elimina SQL Server de la infra/config. Fase 1 (despliegue + config); el código de repos/provider queda para una fase 2 planificada.
Contexto
El chart
infra/local/kubernetes/helm/umsdesplegaba SQL Server como BD del clusterevolith-ums-cluster, inconsistente con el producto (que corre sobre PostgreSQL: appsettings Dev/UAT,evolith.yaml, y la fuenteunimar-ums).Cambios
ums: eliminadotemplates/sqlserver.yaml; añadidotemplates/postgres.yaml(postgres:15-alpine, svcpostgres, PVC pgdata).api.yaml→Host=postgres,Persistence__Provider=PostgreSql+UsePostgreSql*Stores.values.yaml: bloque sqlserver → postgres.ProviderSqlServer → PostgreSql (era el único entorno con SQL Server activo).accesos_local.md(port-forwardsvc/postgres:5432),plan_es.md(puerto 5432).patch_compose.py,patch_di.py).Validación
helm templaterenderiza el chart en Postgres; JSON válido. No se toca el código .NET (losSqlServer*Repositoryson los repos relacionales activos de Postgres — su renombrado/limpieza es la fase 2, documentada).Pendiente (fase 2, código — mayor riesgo)
Renombrar/consolidar los 20
SqlServer*Repository(activos, usados por Postgres), retirar el setPostgreSql*Repositorymuerto, el enumPersistenceProvider.SqlServer, la ramaUseSqlServerdel DbContext, migraciones.sql, paquetes NuGet ySqlServerSchemaBootstrapper/SqlServerDistributedLockProvider, con validación contra Postgres real.🤖 Generated with Claude Code