#durrell_cli-connect

1 messages ยท Page 1 of 1 (latest)

vital sphinxBOT
#

๐Ÿ‘‹ Welcome to your new thread!

โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

๐Ÿ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1288214282751971368

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

viscid flicker
#

durrell0786_cli-connect

#

durrell_cli-connect

vital sphinxBOT
frosty topaz
#

please don't leave me. I'm trying things out ๐Ÿ™

acoustic marlin
#

Don't worry, take your time

frosty topaz
#

In one terminal I'm using the --forward-to flag and in another terminal I'm using the --forward-connect-to flag. The platform events are going to a separate endpoint than the connect events, however the connect events are going to both endpoints. Is this behavior what the docs for the --forward-connect-to flag mean when they say "By default, the same URL will be used for all webhook events."?

Interestingly, both terminals are showing the same signing secret.

#

I wonder whether --load-from-webhooks-api would also allow the connect events to go to a separate endpoint without also going to the platform account endpoint, assuming I configured the endpoints in the dashboard that way.

acoustic marlin
#

Hmm, I've not tested the CLI webhooks in such a way before so I don't know what the expected behavior is.

The doc means to say that if you don't set --forward-connect-to to a different URL, same URL would be use for connect/non-connect events

frosty topaz
#

Oh, I'm supposed to execute both of the flags in the same command, instead of running the cli with the different flags in separate terminals. It's working wonderfuly now. thank you!