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

Open
#787 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api, backend, cli

Research direction

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.

Written by the indexing model from the issue text.

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.
Dominant language
Python
Stars
59
Forks
32
Avg merge
1d 5h
Merged PRs (30d)
76

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-durable-execution-sdk-python

All issues in aws/aws-durable-execution-sdk-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.