73f29ec3a4
Job cluster-gate -> helm-deploy con if needs.cluster-gate.outputs.ready=='true'. Sin KUBECONFIG_TENANT_B64 (cluster aprovisionando) el deploy queda SKIPPED, no rojo. tenant-manager (fase 2 deploy-ready) dispara workflow_dispatch al sembrar el kubeconfig -> run #2 despliega. Sincronizado desde coralware/IDP commit a27e153. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
195 lines
8.0 KiB
YAML
195 lines
8.0 KiB
YAML
name: __APP_NAME__ — build & deploy
|
|
|
|
# Workflow self-contained del golden path (ADR-061): calidad + build + push +
|
|
# helm-deploy inline, SIN `uses:` cross-repo al repo privado `coralware/IDP`.
|
|
# El repo del tenant es un repo cliente — su CI no comparte el ciclo de release
|
|
# del IDP ni el GitOps de Fleet; se construye leyendo solo su propio repo.
|
|
# Corre sobre los runners `[self-hosted, buildkit]` de ci-system (executor=host,
|
|
# buildkit remoto — sin Docker daemon local; ADR-043).
|
|
|
|
on:
|
|
push:
|
|
branches: [main]
|
|
paths:
|
|
- 'code/**'
|
|
- 'helm/**'
|
|
- '.gitea/workflows/__APP_NAME__-build.yaml'
|
|
workflow_dispatch: {}
|
|
|
|
jobs:
|
|
# ── Calidad + build + push de imagen a Harbor ────────────────────────────
|
|
build:
|
|
name: Calidad + build + push
|
|
runs-on: [self-hosted, buildkit]
|
|
outputs:
|
|
image_tag: ${{ steps.meta.outputs.tag }}
|
|
defaults:
|
|
run:
|
|
working-directory: code
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Crear venv e instalar dependencias
|
|
# --system-site-packages reutiliza ruff/black/bandit/pytest ya
|
|
# preinstalados en la imagen del runner; el venv añade las deps de la app.
|
|
run: |
|
|
python3 -m venv --system-site-packages /tmp/venv-__APP_NAME__
|
|
/tmp/venv-__APP_NAME__/bin/pip install --no-cache-dir -r requirements-dev.txt
|
|
|
|
- name: Lint (ruff)
|
|
run: ruff check app
|
|
|
|
- name: Formato (black --check)
|
|
run: black --check app
|
|
|
|
- name: Seguridad (bandit)
|
|
run: bandit -c pyproject.toml -r app --severity-level medium
|
|
|
|
- name: Tests con cobertura
|
|
run: |
|
|
/tmp/venv-__APP_NAME__/bin/python -m pytest tests/ -v \
|
|
--cov=app --cov-report=term-missing --cov-fail-under=80
|
|
|
|
- name: Metadata de imagen
|
|
id: meta
|
|
run: echo "tag=${{ gitea.sha }}" >> "$GITHUB_OUTPUT"
|
|
|
|
- name: Build y push a Harbor
|
|
# Proyecto Harbor del tenant: `t-<tenant-id-short>` (ADR-019 D-03).
|
|
# Credenciales: robot scoped push/pull SOLO a ese proyecto, sembrado
|
|
# por tenant-manager en el repo del tenant (paso 3 del reconcile).
|
|
env:
|
|
REGISTRY: registry.coralsafety.com
|
|
ROBOT_USER: ${{ secrets.HARBOR_ROBOT_USER }}
|
|
ROBOT_TOKEN: ${{ secrets.HARBOR_ROBOT_TOKEN }}
|
|
IMAGE: t-__TENANT_ID_SHORT__/__APP_NAME__
|
|
TAG: ${{ steps.meta.outputs.tag }}
|
|
run: |
|
|
if [ -z "$ROBOT_USER" ] || [ -z "$ROBOT_TOKEN" ]; then
|
|
echo "ERROR: secrets HARBOR_ROBOT_USER/HARBOR_ROBOT_TOKEN no configurados."
|
|
echo "tenant-manager debe sembrarlos al crear el repo (paso 3 del reconcile)."
|
|
exit 1
|
|
fi
|
|
printf '%s' "$ROBOT_TOKEN" | docker login "$REGISTRY" -u "$ROBOT_USER" --password-stdin
|
|
# Builder buildx remoto — apunta al buildkit daemon de ci-system
|
|
# (el runner no tiene Docker daemon local).
|
|
if ! docker buildx inspect tenant-builder >/dev/null 2>&1; then
|
|
docker buildx create --name tenant-builder --driver remote --use \
|
|
"${BUILDKIT_HOST:-tcp://buildkitd.ci-system.svc.cluster.local:2375}"
|
|
else
|
|
docker buildx use tenant-builder
|
|
fi
|
|
docker buildx build --platform linux/amd64 \
|
|
-t "${REGISTRY}/${IMAGE}:${TAG}" \
|
|
--push .
|
|
|
|
# ── Gate de cluster listo (GOLDEN-PATH-BUILD-DEPLOY-ORDER-RACE) ──────────
|
|
# El kubeconfig (secret KUBECONFIG_TENANT_B64) lo siembra tenant-manager en su
|
|
# fase 2 (deploy-ready) cuando el cluster RKE2 del tenant está Ready (~8 min).
|
|
# En el primer run (disparado por el commit de bootstrap) el cluster aún se
|
|
# está aprovisionando: este gate marca `ready=false` → el job helm-deploy se
|
|
# SKIPEA (no falla, no rojo). La imagen ya quedó publicada en el job build.
|
|
# tenant-manager dispara automáticamente un segundo run (workflow_dispatch) al
|
|
# sembrar el kubeconfig → ahí helm-deploy corre y la app queda viva.
|
|
cluster-gate:
|
|
name: ¿Cluster del tenant listo?
|
|
needs: build
|
|
runs-on: [self-hosted, buildkit]
|
|
outputs:
|
|
ready: ${{ steps.check.outputs.ready }}
|
|
steps:
|
|
- name: Verificar kubeconfig sembrado
|
|
id: check
|
|
env:
|
|
KUBECONFIG_B64: ${{ secrets.KUBECONFIG_TENANT_B64 }}
|
|
run: |
|
|
if [ -z "$KUBECONFIG_B64" ]; then
|
|
echo "::notice::Imagen publicada en Harbor ✅. El cluster del tenant se está aprovisionando (~8 min); el deploy se ejecutará automáticamente cuando esté listo (run #2)."
|
|
echo "ready=false" >> "$GITHUB_OUTPUT"
|
|
else
|
|
echo "ready=true" >> "$GITHUB_OUTPUT"
|
|
fi
|
|
|
|
# ── Deploy al cluster del tenant — Helm upgrade --install (sin hook Alembic) ─
|
|
# El runner corre executor=host: los steps se ejecutan directo sobre el pod
|
|
# runner, sin `container:`. helm se instala en runtime.
|
|
# Solo corre cuando el cluster está listo (cluster-gate). En caso contrario el
|
|
# job aparece como skipped (no failure) — separa "imagen publicada" de
|
|
# "app desplegada" como dos hitos.
|
|
helm-deploy:
|
|
name: Helm upgrade --install
|
|
needs: [build, cluster-gate]
|
|
if: needs.cluster-gate.outputs.ready == 'true'
|
|
runs-on: [self-hosted, buildkit]
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- name: Instalar helm
|
|
run: |
|
|
HELM_VERSION=v3.14.4
|
|
case "$(uname -m)" in
|
|
x86_64) ARCH=amd64 ;;
|
|
aarch64) ARCH=arm64 ;;
|
|
*) echo "Arquitectura no soportada: $(uname -m)"; exit 1 ;;
|
|
esac
|
|
mkdir -p "${HOME}/.local/bin"
|
|
curl -fsSL "https://get.helm.sh/helm-${HELM_VERSION}-linux-${ARCH}.tar.gz" \
|
|
| tar -xz -C /tmp "linux-${ARCH}/helm"
|
|
mv "/tmp/linux-${ARCH}/helm" "${HOME}/.local/bin/helm"
|
|
chmod +x "${HOME}/.local/bin/helm"
|
|
echo "${HOME}/.local/bin" >> "$GITHUB_PATH"
|
|
"${HOME}/.local/bin/helm" version
|
|
|
|
- name: Decodificar kubeconfig del tenant
|
|
env:
|
|
KUBECONFIG_B64: ${{ secrets.KUBECONFIG_TENANT_B64 }}
|
|
run: |
|
|
if [ -z "$KUBECONFIG_B64" ]; then
|
|
echo "ERROR: secret KUBECONFIG_TENANT_B64 no configurado en el proyecto Gitea."
|
|
echo "tenant-manager debe provisionarlo al crear el repo."
|
|
exit 1
|
|
fi
|
|
mkdir -p "${HOME}/.kube"
|
|
echo "$KUBECONFIG_B64" | base64 -d > "${HOME}/.kube/config"
|
|
chmod 600 "${HOME}/.kube/config"
|
|
|
|
- name: Helm upgrade --install
|
|
env:
|
|
TENANT_ID: ${{ vars.TENANT_ID }}
|
|
TENANT_ID_NODASHES: ${{ vars.TENANT_ID_NODASHES }}
|
|
TENANT_TIER: ${{ vars.TENANT_TIER }}
|
|
IMAGE_TAG: ${{ needs.build.outputs.image_tag }}
|
|
# ADR-054: namespace funcional fijo en cluster tenant — el cluster ya es el sandbox.
|
|
run: |
|
|
helm upgrade --install __APP_NAME__ ./helm/__APP_NAME__ \
|
|
--namespace apps \
|
|
--create-namespace \
|
|
--set image.tag=${IMAGE_TAG} \
|
|
--set tenantId=${TENANT_ID} \
|
|
--set tenantIdNodashes=${TENANT_ID_NODASHES} \
|
|
--set tier=${TENANT_TIER} \
|
|
--wait --timeout 5m
|
|
|
|
- name: Verificar rollout
|
|
run: |
|
|
kubectl -n apps rollout status deploy/__APP_NAME__ --timeout=3m
|
|
|
|
- name: Smoke check post-deploy
|
|
# FQDN con tenant-id CON guiones — coincide con el A record que crea
|
|
# cloudflare-provisioner y con el host del Ingress NGINX
|
|
# (helm/APP_NAME/values.yaml). Paridad ADR-053 §11.1.
|
|
env:
|
|
INGRESS_HOST: __APP_NAME__-${{ vars.TENANT_ID }}.apps.coralware.cloud
|
|
run: |
|
|
for i in $(seq 1 12); do
|
|
if wget -q -O - --timeout=10 "https://${INGRESS_HOST}/health" | grep -q '"status":"ok"'; then
|
|
echo "Smoke OK: /health responde 200"
|
|
exit 0
|
|
fi
|
|
echo "Intento ${i}/12 — /health aún no responde, esperando 5s…"
|
|
sleep 5
|
|
done
|
|
echo "ERROR: /health no respondió 200 dentro del timeout"
|
|
exit 1
|