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: flag streams as pull created for auth header in webhook #2064

Merged
merged 3 commits into from
Feb 19, 2024

Conversation

gioelecerati
Copy link
Member

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

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 19, 2024 15:35
Copy link

vercel bot commented Feb 19, 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 19, 2024 4:10pm

@gioelecerati gioelecerati merged commit 61d6864 into master Feb 19, 2024
13 checks passed
@gioelecerati gioelecerati deleted the gio/stream/flag-pull-created branch February 19, 2024 16:41
Comment on lines +475 to +480
isPullStream:
type: boolean
readOnly: true
description: >-
Wether the stream is authenticated by Trovo. If true, any webhook
policy will include the Trovo Auth header
Wether the stream is a pull stream. If true, any webhook policy will
include the Trovo Auth header
Copy link
Member

@victorges victorges Feb 20, 2024

Choose a reason for hiding this comment

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

We can already tell this by the existence of the pull field, so this is redundant. It should also be omitted from API schema not to pollute our public documentation. So you can move this to db-schema or just omit from the schema altogether (tho I guess this would break typescript stuff, unless you start using the stream.pull for it).

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