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

Ouverte
#787 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
python
Domaine
api, backend, cli

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Python
Étoiles
59
Forks
32
Merge moyen
1 j 5 h
PR mergées (30 j)
76

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de aws/aws-durable-execution-sdk-python

Toutes les issues de aws/aws-durable-execution-sdk-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.