pan triggers
Available from the next release.
~/.overdeck/triggers.json directly, and the
dashboard reads that file on every event. See Webhook triggers.
add
Pass exactly one of
--conversation and --project; otherwise it exits 1. An unknown
conversation or project exits 1.
It prints the hook path, the local test URL (http://127.0.0.1:<port>/hooks/…), the Funnel
URL (https://<machine>.<tailnet>.ts.net:8443/hooks/… unless a .ts.net address is saved),
any generated signing secret, the Funnel command, and then:
list
ID NAME TARGET VERIFY SIGNING SECRET CREATED. TARGET is
conversation <name> or project <key>; SIGNING SECRET is secret set or
secret not set for github and stripe triggers. It never prints a secret.
With no triggers:
`No triggers. Create one with `pan triggers add`.`
remove
404 from the next event on:
No trigger with id <id>. and exits 1.
set-secret
github or stripe trigger, for example a Stripe endpoint’s
whsec_… secret. Without --secret it reads one line from standard input, so the secret
stays out of your shell history:
An empty value exits 1. An unknown id prints
No trigger with id <id>. and exits 1.