Skip to content

Feature/workflow trigger http - #616

Draft
anirudhwarrier wants to merge 2 commits into
mainfrom
feature/workflow-trigger-http
Draft

anirudhwarrier wants to merge 2 commits into
mainfrom
feature/workflow-trigger-http

Conversation

@anirudhwarrier

Copy link
Copy Markdown
Contributor

No description provided.

anirudhwarrier and others added 2 commits October 1, 2026 00:09
The upcoming trigger command takes user payloads via --input, either inline or as a local file path. Redact it like http-payload so neither reaches telemetry.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Add `cre workflow trigger http <workflow-folder-path>` so a live E2E suite can fire a deployed workflow's HTTP trigger through the CRE Gateway using only the cre binary.

The command signs a `workflows.execute` JSON-RPC request with the CRE_ETH_PRIVATE_KEY wallet using the node's own JWT helper (ETH alg, request digest, single-use jti), posts it with an Authorization Bearer header to the vault gateway URL (the same endpoint serves the workflows service), and prints a stable JSON result with --json. The workflow ID is resolved like `workflow get` unless --workflow-id is given. The command group is hidden from help and docs.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
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