Skip to content

feat(sdk): add executionInput to InvocationInfo (plugin interface)#653

Merged
ParidelPooya merged 4 commits into
mainfrom
feat/plugin-execution-input-on-start
Jun 19, 2026
Merged

feat(sdk): add executionInput to InvocationInfo (plugin interface)#653
ParidelPooya merged 4 commits into
mainfrom
feat/plugin-execution-input-on-start

Conversation

@ParidelPooya

@ParidelPooya ParidelPooya commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Moves executionInput from InvocationEndInfo up to InvocationInfo so plugins receive the execution input on onInvocationStart — not only at invocation end.

Motivation

Observability plugins (like Workflow Insight) need to include the execution input in their first emitted record. Currently executionInput is only available in onInvocationEnd, which means:

  • The initial RUNNING record has no input
  • If the execution suspends (wait/callback) before completing, no record ever has the input

Moves executionInput from InvocationEndInfo up to InvocationInfo so
plugins receive the execution input on onInvocationStart — not only
at invocation end. This enables observability plugins to include
the input in their first emitted record.

Changes:
- InvocationInfo: added executionInput field
- InvocationEndInfo: removed duplicate (now inherited)
- with-durable-execution.ts: moved customerHandlerEvent parsing
  before invocationInfo construction and onInvocationStart call
- Updated test assertions to include the new field
Comment thread packages/aws-durable-execution-sdk-js-otel/src/__tests__/plugin.test.ts Outdated
The field is required by InvocationInfo (parent type), not a
duplicate from InvocationEndInfo. Added comment for clarity.
@ParidelPooya
ParidelPooya merged commit 294a757 into main Jun 19, 2026
57 of 63 checks passed
@ParidelPooya
ParidelPooya deleted the feat/plugin-execution-input-on-start branch June 19, 2026 18:31
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.

2 participants