Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Staging deployments do not promote their tested Simulation Entrypoint revision

Abierto
  • ¿Algo no está bien?
#893 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@anth-volk ya está trabajando en esto.

Desde el 21/10/2026.

  • #894 de @anth-volk — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
docker, github-actions, python
Área
ci-cd, cloud, devops

Línea de trabajo

Read .github/workflows/simulation-deploy.yml and .github/workflows/stage12-deploy.yml, then trace the staging promotion checks and cleanup rules described in the issue. Confirm how the operator's initial traffic move affects the stable-URL check before changing the staging settings. Done means both staging paths promote the tested revision, a registered rule enforces promotion, and the existing rollback and checks still work.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What

Staging deployments of the Simulation Entrypoint test a tagged Cloud Run candidate but never move the staging service's stable traffic to it. Both the beta job in simulation-deploy.yml and the staging job of the Stage 12 comparison path workflow (stage12-deploy.yml) pass promote_entrypoint: false. Production deployments pass true.

As a result, the staging service's stable URL does not serve the build that passed the staging tests. Today it serves Cloud Run's sample container (revision 00001-cuh), whose /health returns an HTML page with no revision header, and every tested staging build exists only behind a tagged URL that receives no stable traffic.

Why it matters

Any caller that uses the staging stable URL reaches an untested build, or the sample container, instead of the build the deployment tested. This prevents staging callers, such as the Public API's staging service, from running their own staging checks against staging simulation infrastructure.

Wanted result

  • Every staging deployment promotes its tested entrypoint revision to the staging service's stable traffic, as production does, using the same checks: exact revision change, stable-URL checks, authentication checks and restoring the previous revision on failure.
  • A registered rule requires it, so a staging deployment cannot go back to leaving stable traffic unchanged.
  • Expected side effect: after the first promotion, the existing clean-up deletes the staging service's older revisions (about 67 today), keeping only the promoted revision and the one it replaced.

Order

Before the change merges, an operator must move the staging stable traffic off the sample container onto a tested staging revision. Otherwise the first promotion's stable-URL check fails on the sample container's response, restores it, and fails the beta deployment, which stops the production deployment.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
1 d 16 h
PR fusionados (30 d)
60

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de PolicyEngine/policyengine-sim-api

Todos los issues de PolicyEngine/policyengine-sim-api

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.