devops/apps-registry
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(ci): actualizar MANIFEST_FILE tras la migracion a platform-templates
Build and Push Medusa / Escaneo de Secretos (Gitleaks) (push) Successful in 22s
Details
Build and Push Frontend / Escaneo de Secretos (Gitleaks) (push) Successful in 22s
Details
Build and Push Docs Portal / Escaneo de Secretos (Gitleaks) (push) Successful in 20s
Details
Build and Push Medusa / Construir y publicar Medusa (push) Successful in 19m12s
Details
Build and Push Frontend / Construir y Subir Imagen (push) Successful in 10m5s
Details
Build and Push Docs Portal / Construir y publicar Docs Portal (push) Successful in 4m55s
Details

Browse Source 
Los 3 pipelines (build.yaml, build-medusa.yaml, deploy-docs.yaml)
todavia apuntaban a las rutas viejas de deployment.yaml (borradas al
migrar cada app a un overlay de platform-templates) para el paso de
auto-actualizacion GitOps. Se rompio en vivo en el primer build real
post-migracion (docs-portal v1.0.117): la imagen se construyo, escaneo
y firmo bien, pero el ultimo paso (sed sobre el manifest) fallo con
'No such file or directory'. Se corrigen las 3 rutas a
patches/deployment.yaml, y se bumpea a mano el tag de docs-portal a
v1.0.117 (la imagen ya existe en el registry, firmada y verificada,
no hace falta reconstruirla).

Co-Authored-By: Claude Sonnet 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_011FqYP3Wf1W63Qmh7qgXAAT
This commit is contained in:
devopsandClaude Sonnet 5 committed 2026-08-17 01:03:41 -05:00
1 parent 837446ba16
commit 42e6250adc
4 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.gitea/workflows/build-medusa.yaml
+1 -1
View File
@@ -84,7 +84,7 @@ jobs:
env: env:
APP_DIR: workloads/commerce-backend APP_DIR: workloads/commerce-backend
MANIFEST_FILE: workloads/ecommerce/commerce/medusa.yaml MANIFEST_FILE: workloads/ecommerce/commerce/medusa/patches/deployment.yaml
IMAGE_NAME: gitea.cruzcloud.net/devops/ecommerce-medusa IMAGE_NAME: gitea.cruzcloud.net/devops/ecommerce-medusa
steps: steps:
.gitea/workflows/build.yaml
+1 -1
View File
@@ -126,7 +126,7 @@ jobs:
env: env:
APP_DIR: workloads/ecommerce APP_DIR: workloads/ecommerce
MANIFEST_FILE: workloads/ecommerce/frontend.yaml MANIFEST_FILE: workloads/ecommerce/frontend/patches/deployment.yaml
IMAGE_NAME: gitea.cruzcloud.net/devops/ecommerce-frontend IMAGE_NAME: gitea.cruzcloud.net/devops/ecommerce-frontend
steps: steps:
.gitea/workflows/deploy-docs.yaml
+1 -1
View File
@@ -84,7 +84,7 @@ jobs:
env: env:
APP_DIR: workloads/docs-portal APP_DIR: workloads/docs-portal
MANIFEST_FILE: workloads/docs-portal/deployment.yaml MANIFEST_FILE: workloads/docs-portal/patches/deployment.yaml
IMAGE_NAME: gitea.cruzcloud.net/devops/docs-portal IMAGE_NAME: gitea.cruzcloud.net/devops/docs-portal
steps: steps:
workloads/docs-portal/patches/deployment.yaml
+1 -1
View File
@@ -25,7 +25,7 @@ spec:
runAsNonRoot: false runAsNonRoot: false
containers: containers:
- name: app - name: app
image: gitea.cruzcloud.net/devops/docs-portal:v1.0.116 image: gitea.cruzcloud.net/devops/docs-portal:v1.0.117
# El base saca TODAS las capabilities. Probado en vivo y # El base saca TODAS las capabilities. Probado en vivo y
# revertido: con drop: ALL (aunque se agregue NET_BIND_SERVICE # revertido: con drop: ALL (aunque se agregue NET_BIND_SERVICE
# de vuelta) el propio entrypoint de nginx:1.27-alpine falla al # de vuelta) el propio entrypoint de nginx:1.27-alpine falla al