Skip to content

Add plugin-suite conformance handlers for requirements 10-8..10-19 - #601

Draft
wangyb-A wants to merge 4 commits into
mainfrom
plugin-suite-edge-cases
Draft

Add plugin-suite conformance handlers for requirements 10-8..10-19#601
wangyb-A wants to merge 4 commits into
mainfrom
plugin-suite-edge-cases

Conversation

@wangyb-A

@wangyb-A wangyb-A commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds 11 conformance handlers (handlers/plugin/plugin_operation_change.py through plugin_wait_replay_flag.py) plus template_plugin.yaml entries implementing plugin-suite requirements 10-8..10-18 from aws/aws-durable-execution-conformance-tests#43 (land that PR first — the pinned runner must carry the requirement YAMLs before CI can resolve these IDs).

All handlers use real SDK APIs only: real retry strategies, real context.wait / context.parallel / run_in_child_context, real DurableInstrumentationPlugin registration — no mocked behavior. Records are bare-JSON stdout lines stamped with durableExecutionArn (captured from on_invocation_start) for the runner's CloudWatch filter.

Note on 10-9: Python surfaces externally-updated operations via on_operation_end during replay (not on invocation-start info); the requirement's hook-agnostic wording explicitly permits this — documented in the handler.

Validation (us-west-2, live deploy)

18/18 PASS — all 11 new requirements plus full 10-1..10-7 regression.

@wangyb-A
wangyb-A force-pushed the plugin-suite-edge-cases branch from a4ca93e to fef9273 Compare July 31, 2026 19:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant