[Feature]: Add pause/resume to the local runner HTTP API and CLI

Abierto
#787 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
python
Área
api, backend, cli

Línea de trabajo

Start by reading the web runner and HTTP route implementations, the dex-local-runner CLI entry points, and the pause/resume behavior introduced by #757. Define the HTTP and CLI contracts, including bounded waits and error handling, then add unit tests for routes and CLI arguments and E2E coverage for pause and resume. Done means an in-flight local execution can be paused and resumed through both interfaces, with documented behavior for timeouts and invalid or completed executions.

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

Descripción

parity pkg:testing
What would you like?

Expose execution pause and resume through the local emulator's HTTP API and the dex-local-runner CLI.

This follows the request in the approval of PR #757. It is separate work, not a merge requirement for that PR.

The reviewer notes that SAM CLI runs the emulator as a container and calls its HTTP routes. Adding these routes would let SAM CLI add pause/resume commands in a separate change.

Possible Implementation
  • Add pause/resume support to the web runner and its HTTP routes.
  • Add CLI commands that call those routes for a specified execution ARN.
  • Reuse the pause/resume behavior introduced by #757.
  • Define request and response formats, timeout behavior, and error mapping.
  • Document HTTP and CLI usage, including the experimental status of these controls.
Acceptance criteria
  • Users can pause and resume a local execution through HTTP and through the CLI.
  • Pause waits are bounded. A timeout clearly reports that the pause request remains applied.
  • Repeated requests, completed executions, invalid ARNs, and unknown executions have documented behavior consistent with the underlying runner.
  • Unit tests cover routes, CLI argument handling, and error responses.
  • E2E tests cover pausing an in-flight execution and resuming it to completion through the HTTP API and CLI.
Is this a breaking change?

No. This adds local testing controls.

Does this require an RFC?

No RFC is proposed. Confirm the HTTP and CLI contracts during implementation.

Additional Context
  • Follow-up to #757.
  • SAM CLI changes belong in a separate follow-up. This issue provides the emulator support they would need.
Lenguaje dominante
Python
Estrellas
59
Forks
32
Merge medio
1 d 5 h
PR fusionados (30 d)
76

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 aws/aws-durable-execution-sdk-python

Todos los issues de aws/aws-durable-execution-sdk-python

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.