Open cavis opened 7 years ago
Tried this briefly, while working on something else.
More complex than I initially thought. Even if you PUT the status: "uploaded"
, CMS doesn't actually listen to that. Instead, it updates timestamps (as with any PUT request), fires off SNS, and waits for the lambda-sqs-callback to change the status/statusMessage.
When retrying the audio lambda, we should PUT
{status: "uploaded"}
back to CMS to kick it off, rather than an empty object. Both kick off the lambda, but reseting the status to uploaded makes sure Publish keeps pinging for status changes until the lambda completes.