Workflow Execution Commands#460
Conversation
|
👋 ejacquier, thanks for creating this pull request! To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team. Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks! |
|
| Version | Value |
|---|---|
| Current Fork | v1.17.0 |
| Latest Upstream | null |
Action Required
- Review abigen changes in upstream (only the
accounts/abi/binddirectory matters) - Compare with our fork in
cmd/generate-bindings/bindings/abigen/ - If relevant changes exist, sync them and update
FORK_METADATA.md - If no abigen changes, just update the version in
FORK_METADATA.mdtonull
Files to Review
cmd/generate-bindings/bindings/abigen/bind.gocmd/generate-bindings/bindings/abigen/bindv2.gocmd/generate-bindings/bindings/abigen/template.go
cc @smartcontractkit/bix-framework
|
| Version | Value |
|---|---|
| Current Fork | `` |
| Latest Upstream | v1.17.3 |
Action Required
- Review abigen changes in upstream (only the
accounts/abi/binddirectory matters) - Compare with our fork in
cmd/generate-bindings/bindings/abigen/ - If relevant changes exist, sync them and update
FORK_METADATA.md - If no abigen changes, just update the version in
FORK_METADATA.mdtov1.17.3
⚠️ Potential Security-Related Commits Detected
- p2p/nat: bump pion/stun to v3 to pull in fixed pion/dtls (#34980) (link)
- build: upgrade -dlgo version to Go 1.25.10 (#34911) (link)
Files to Review
cmd/generate-bindings/bindings/abigen/bind.gocmd/generate-bindings/bindings/abigen/bindv2.gocmd/generate-bindings/bindings/abigen/template.go
cc @smartcontractkit/bix-framework
|
| Version | Value |
|---|---|
| Current Fork | `` |
| Latest Upstream | v1.17.3 |
Action Required
- Review abigen changes in upstream (only the
accounts/abi/binddirectory matters) - Compare with our fork in
cmd/generate-bindings/bindings/abigen/ - If relevant changes exist, sync them and update
FORK_METADATA.md - If no abigen changes, just update the version in
FORK_METADATA.mdtov1.17.3
⚠️ Potential Security-Related Commits Detected
- p2p/nat: bump pion/stun to v3 to pull in fixed pion/dtls (#34980) (link)
- build: upgrade -dlgo version to Go 1.25.10 (#34911) (link)
Files to Review
cmd/generate-bindings/bindings/abigen/bind.gocmd/generate-bindings/bindings/abigen/bindv2.gocmd/generate-bindings/bindings/abigen/template.go
cc @smartcontractkit/bix-framework
Summary
Adds
cre workflow execution— a new subcommand group that surfaces workflow execution history, capability events, and logs from the CRE platform directly in the terminal, without needing a browser or leaving a workflow folder.Also adds
cre workflow status— a workflow-level health command that combines deployment state, execution summary, and last execution detail in a single view, with specific visibility into the gap between registering a workflow and it becoming active in the DON.New commands
cre workflow status <workflow-id-or-name>workflows+workflowDeployments+workflowExecutionscre workflow execution list [workflow-id-or-name]workflowExecutionscre workflow execution status <execution-id>workflowExecution+workflowExecutionEventscre workflow execution events <execution-id>workflowExecutionEvents--capabilityand--status.cre workflow execution logs <execution-id>workflowExecutionLogs--node(client-side).All commands support
--output=jsonand--jsonfor machine-readable output.cre workflow listalso gains--json.Flags
--limit Nexecution list--start/--endexecution list--statusexecution listTRIGGERED,IN_PROGRESS,SUCCESS,FAILURE--capabilityexecution events--statusexecution events--nodeexecution logs--output json/--jsonIdentifier consistency
All commands use the same identifiers visible in the Explorer UI and
cre workflow list. Internal platform UUIDs are not shown in table output but are preserved in--jsonoutput for scripting and automation.00da21b8...), shown incre workflow list1d24bfa2...), shown in the Explorer UIBoth formats are accepted as input. UUID resolution happens internally and is never surfaced.
Implementation notes
workflow.yamlrequired--nodefiltering on logs is client-side — the platform API (workflowExecutionLogs) does not expose a server-side node filterTRIGGERED,IN_PROGRESS,SUCCESS,FAILURE) — the PRD had incorrect values (RUNNING,PENDING,RECOVERY_PAUSED)cre workflow statusmakes 5 parallel API calls (workflow summary, latest deployment, last execution, success count, failure count); non-fatal errors are surfaced as warnings rather than silently swallowedworkflowDeploymentsrequiresfrom/todate fields despite the schema marking them optional — backend bug filed separatelycre workflow listandcre workflow deploynow surface contextualcre workflow executioncommands —listafter displaying workflows,deployon successful deployment