Open leggetter opened 7 months ago
They * could cause problem if there are thousands of sources, should we put a upper bound of the first 100 as a limitation?
Yes, let's add a limitation.
@leggetter do we want to support the case where events from different connections / destinations are routed to different ports?
@leggetter do we want to support the case where events from different connections / destinations are routed to different ports?
For now, no. I think it's fine to expect a new process to be spun up to send events to different ports.
How
*
select to thelisten
command. Right now you can dohookdeck listen 9001 shopify
which starts the CLI without a source select prompt for the source specified. Withhookdeck listen 9001 *
we could let you select all sourceshookdeck listen 9001 shopify,stripe
to start on a set of sourceshookdeck listen 9001
the source select prompt should have a “all” option which has the same behavior as*
shopify -> out-of-stock
The backend should already support this as only a set of connection IDs are expected
Caveat & questions
They
*
could cause problem if there are thousands of sources, should we put a upper bound of the first 100 as a limitation?