Some sync flows include the sync ID as a search param (named deployId) sent to the SDK. The API expects the sync ID to be sent as a search param when the SDK sends its sync request.
Also, the sync ID must not appear in the function URLs, since this would change the checksum
Description
When the SDK receives a sync request, extract and use the optional sync ID from the URL
Context
This is related to this section of the SDK spec: https://github.com/inngest/inngest/blob/main/docs/SDK_SPEC.md#432-syncing
Some sync flows include the sync ID as a search param (named
deployId) sent to the SDK. The API expects the sync ID to be sent as a search param when the SDK sends its sync request.Also, the sync ID must not appear in the function URLs, since this would change the checksum