Expected Behavior

I can easily test out their Trigger config e.g. does the CEL expression work, does my binding expression extract the right variable, does my trigger template replace the right variable etc.

Actual Behavior

I have to setup an EventListener, TriggerBinding, and TriggerTemplate. I have to port-forward to the Listener, and make a curl call, and then look into the Listener logs to figure out what happened.

Additional Info

Example CLI surface from discussing with @bigkevmcd :

triggers-run -H "X-GitHub-Event: testing" -d @testing.json -f triggers.yaml

1. triggers.yaml is a file containing the trigger definitions
2. The CLI supports curl like flags for sending headers and body
3. The tool will prints out the trigger processing logs to stdout
4. It will also print out the fully formed Tekton resource to be created once the trigger is processed instead of creating them

Out of scope for now:

1. Testing Trigger level service account permissions

Can be added later:

1. Actually create the resources instead of just printing them out
2. Dry run against a already running listener instead of definitions from a file
3. Make it part of the tkn surface e.g. tkn trigger run ....
4. Account for the Trigger service account permissions

Related :

1. TriggerTemplateRun #200
2. Binding eval tool #314

/kind feature