Skip to content
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: webhook: allow additional headers & payload to be sent in webhooks #2053

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

gioelecerati
Copy link
Member

What does this pull request do? Explain your changes. (required)

Allow catalyst to specify two new objects when calling Studio gate

  • webhookPayload
  • webhookHeaders
    They will get appended to the JSON payload and the headers respectively when doing a webhook request for access control to an external party

Also added Trovo-Auth-Version: 1.1 as header to any webhook fired for a stream created via the pull api

Specific updates (required)

How did you test each of these updates (required)

Does this pull request close any open issues?

Screenshots (optional)

Checklist

  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@gioelecerati gioelecerati requested a review from a team as a code owner February 13, 2024 13:45
Copy link

vercel bot commented Feb 13, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
livepeer-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 15, 2024 3:00pm

@gioelecerati gioelecerati merged commit d184f30 into master Feb 15, 2024
13 checks passed
@gioelecerati gioelecerati deleted the gio/api/customized-webhook-payload branch February 15, 2024 16:36
}

if (isTrovoAuth) {
params.headers["Trovo-Auth-Version"] = "1.1";
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This hurts 😆
Let's make sure to migrate these to per-webhook headers configs later, which Trovo can play around however they want. We should avoid hardcoded logic for specific clients.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants