Hi everyone,
I’m leveraging the B-Deploy API and noticed the url field appears in the POST payloads for both the /setup and /player endpoints. We populate this field with a time-limited, signed S3 URL that hosts our deployment package.
I’d appreciate some guidance on three points:
-
Functional differences – Does the url parameter behave identically in /setup and /player, or are there subtle differences in how each endpoint processes it?
-
Use cases – In practice, when should we target /setup versus /player for a deployment triggered via a signed URL?
-
URL expiry – What happens if the signed S3 URL expires before the player finishes downloading the package? Does the B-Deploy service retry, cache, or surface an error we can catch?
Understanding the intended workflow will help us choose the right endpoint and set an appropriate expiry window for our signed URLs.
Thanks in advance for any insights or best practices you can share!
