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

feat(replays): Add denylist feature handling for replay video #3803

Merged
merged 12 commits into from
Jul 10, 2024

Conversation

cmanallen
Copy link
Member

Adds a pre-processing step to ReplayGroup processing. The envelope items are iterated over and if a replay-video event is found processing exits early before the items are processed.

This feature should always default to enabled. It should only return the disabled state if the feature was successfully evaluated and the organization was found to be explicitly denied access.

I'm not familiar with all the implications these code paths have. If someone with more knowledge and experience could double-check my work I would appreciate it.

Related: https://github.com/getsentry/getsentry/pull/14569
Related: getsentry/sentry#73981

@cmanallen cmanallen requested a review from a team as a code owner July 9, 2024 15:44
relay-dynamic-config/src/feature.rs Outdated Show resolved Hide resolved
relay-server/src/services/processor/replay.rs Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
cmanallen and others added 6 commits July 10, 2024 07:37
Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
@cmanallen cmanallen merged commit f9acbbc into master Jul 10, 2024
23 checks passed
@cmanallen cmanallen deleted the cmanallen/replays-add-video-denylist branch July 10, 2024 14:27
0Calories pushed a commit that referenced this pull request Jul 11, 2024
Adds a pre-processing step to `ReplayGroup` processing. The envelope
items are iterated over and if a replay-video event is found processing
exits early before the items are processed.

This feature should always default to enabled. It should only return the
disabled state if the feature was successfully evaluated and the
organization was found to be explicitly denied access.

I'm not familiar with all the implications these code paths have. If
someone with more knowledge and experience could double-check my work I
would appreciate it.

Related: getsentry/getsentry#14569
Related: getsentry/sentry#73981

---------

Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
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.

2 participants