You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 18, 2024. It is now read-only.
I was looking into this and noticed that taskrun events have examples for queued while the cli does not.
Which of these is correct, the example or the code?
go run main.go taskrun
Emit TaskRun related CloudEvent
Usage:
cde taskrun [command]
Available Commands:
finished Emit TaskRun Finished Event
started Emit TaskRun Started Event
Flags:
-d, --data stringToString Task Run's Data (default [])
-h, --help help for taskrun
-i, --id string Task Run Id
-n, --name string Task Run's Name
-p, --pipelineid string Task Run's Pipeline Id
Global Flags:
--config string config file (default is $HOME/.cde.yaml)
Use "cde taskrun [command] --help" for more information about a command.
In the readme for the SDK we list examples of how to send events. The SDK does support more events than listed in the examples.
To resolve this issue add examples for sending the other event types.
The text was updated successfully, but these errors were encountered: