Move the deploy workflow's routing and sentinel steps into tested scripts

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

Los mantenedores suelen responder en 2 días

Ya se ha fusionado un pull request relacionado.

  • #1004 de @anth-volk — fusionado

Evaluación

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

Línea de trabajo

Start with .github/workflows/simulation-deploy.reusable.yml and the seven named steps, then inspect rules/baselines/ci-multiline-run.txt and the tests that read shell from the workflow YAML. Move each block into a tested script under .github/scripts/, update the tests to run those scripts, and remove the seven baseline entries. Done when all seven steps keep identical behavior and their tests pass.

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

Descripción

Phase 1 step 1.7 of the rules work, follow-up to #763: the seven multi-line run: blocks that #743 and #744 added to .github/workflows/simulation-deploy.reusable.yml move into tested scripts under .github/scripts/, each called from a single-command step, with identical behaviour.

The seven steps:

  • update_routing: Plan the routing change, Record the unfinished routing publication, Publish the planned routing
  • sentinel_expected: Check the sentinel names this deployment's bundle
  • integration: Check the deployed stack reproduces the sentinel numbers
  • promote_entrypoint: Verify the stable service reproduces the sentinel numbers
  • finalize_routing: Finalize the routing publication

#763 left them in rules/baselines/ci-multiline-run.txt (rule sim.ci.multiline-run-is-script) because their tests read the steps' shell from the workflow YAML. Those tests are rewritten to run the scripts, and the seven baseline entries are removed. The six blocks in simulation-rollback.yml follow in a separate pull request.

Lenguaje dominante
Python
Estrellas
1
Forks
1
Merge medio
2 d 48 min
PR fusionados (30 d)
87

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.