-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api: Fix recording webhooks #1360
Conversation
It doens't exist
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov Report
@@ Coverage Diff @@
## master #1360 +/- ##
===================================================
+ Coverage 51.90412% 52.12121% +0.21709%
===================================================
Files 68 68
Lines 4464 4455 -9
Branches 834 829 -5
===================================================
+ Hits 2317 2322 +5
+ Misses 1851 1838 -13
+ Partials 296 295 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM that nothing's obviously off, not intimately familiar with this anymore
What does this pull request do? Explain your changes. (required)
As an exercise of understanding the current recording pipeline as we'll need
to revamp it soon for the catalyst integreation (and since a key customer was
suffering with that), I found some easy improvements we could make to the
recording webhooks in order to make them more useful.
The main changes revolve towards sending the session object with the recording
both on the
started
andready
webhooks. For that, it also required changing thepoint in the code where we send the
recording.started
(but theready
had to staywhere it was).
Specific updates (required)
recording.ready
hook from/setactive
toPOST /stream/:id
(MistProcLivepeer
), where we create the user session objectsession
object to the webhook payload bothstarted
andready
recording.ready
hook.-
Does this pull request close any open issues?
Fixes customer issue.
Screenshots (optional):
https://webhook.site/#!/d5fd9d61-383c-4891-8d10-0e29886fef50/c587140c-a5ae-4b22-a576-7d35f0553ff8/1
Checklist: