Repository navigation
Conversation
* ci(pipeline): integration of scans * fix(pipeline): corrections of .yml * fix(pipeline): corrections of .yml * fix(pipeline): corrections of .yml * fix(pipeline): corrections of yml and Dockerfile * fix(pipeline): corrections of Dockerfile * fix(pipeline): corrections of Dockerfile * fix(pipeline): corrections of ci-pipeline.yml * fix(pipeline): corrections of ci-pipeline.yml * fix(pipeline): corrections of ci-pipeline.yml * feat(pipeline): implementations of the security reports * feat(pipeline): implementations of the security reports * feat(pipeline): implementations of the security reports * feat(pipeline): implementations of the security reports * feat(code/pipeline): corrections init db into the pod and implementation cd actions * feat(deploy): implementation of kubernetes manifest with helm * ci(pipeline): integrate pipeline with hosted jobs * ci(pipeline): bypass scane IaC & Config
* ci(pipeline): bypass scane IaC & Config * ci(pipeline): pipeline refactor changes the steps for environments
…eployment pipeline.
…eployment pipeline.
…eployment pipeline.
… to ci-pipeline trigger
…cker-publish en despliegue de kubernetes
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.
📝 Resumen de Cambios
Se ha realizado una reestructuración integral de los flujos de despliegue y entrega continua (CD), optimizando la segregación de responsabilidades entre los workflows de GitHub Actions. Se implementó un nuevo pipeline dedicado a la construcción y publicación de imágenes, se mejoró la observabilidad en el despliegue de AWS mediante la captura de logs de Terraform y se actualizó exhaustivamente la documentación técnica del proyecto, incluyendo diagramas interactivos de arquitectura.
🚀 Tipo de Cambio
cd-build.ymly nueva documentación técnica.📋 Lista de Cambios Clave
cd-build.yml: Centraliza la construcción con Maven, la publicación en Docker Hub y el escaneo de vulnerabilidades con Trivy.cd-deploy-kb.yml: Eliminación de etapas de build redundantes para enfocarse exclusivamente en el despliegue vía Helm.cd-deploy-cloud.yml: Adición de soporte para ramasdev,testymain, y redirección de salida de Terraform a archivos de log para facilitar la depuración.ci-pipeline.yml: Ampliación de los disparadores de Pull Request para incluir la ramamain.vpc_id), adición de.gitignoreespecífico para Terraform y actualización de archivos de ejemplo.example.env.IaC/.env) del control de versiones.DEMO.mdcon guía de uso y API.README.mdcon una descripción técnica detallada y tabla de workflows.docs/) detallando la arquitectura en AWS ECS y Kubernetes.