Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Staging deployments do not promote their tested Simulation Entrypoint revision

Offen
  • Stimmt etwas nicht?
#893 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@anth-volk arbeitet bereits daran.

Seit 21.10.2026.

  • #894 von @anth-volk — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
docker, github-actions, python
Bereich
ci-cd, cloud, devops

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
Python
Sterne
1
Forks
1
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
60

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PolicyEngine/policyengine-sim-api

Alle Issues in PolicyEngine/policyengine-sim-api

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.