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(flags): Add splitio audit-log provider #79636

Closed
wants to merge 35 commits into from

Conversation

cmanallen
Copy link
Member

Adds split.io as a feature-flag provider.

Ref: https://github.com/getsentry/team-replay/issues/491

@cmanallen cmanallen requested a review from a team as a code owner October 23, 2024 20:49
@cmanallen cmanallen requested a review from a team as a code owner October 23, 2024 20:49
@cmanallen cmanallen changed the base branch from master to mz/ld-provider October 23, 2024 20:50
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Oct 23, 2024
raise InvalidProvider(provider)
if "previous" not in request_data:
action = ACTION_MAP["created"]
elif DELETED_REGEX.match(request_data["description"]):

Check failure

Code scanning / CodeQL

Polynomial regular expression used on uncontrolled data

This [regular expression](1) that depends on a [user-provided value](2) may run slow on strings starting with ' deleted feature ' and with many repetitions of ' deleted feature '.
Copy link

codecov bot commented Oct 23, 2024

Codecov Report

Attention: Patch coverage is 98.68421% with 1 line in your changes missing coverage. Please review.

✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
src/sentry/flags/endpoints/hooks.py 96.87% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master   #79636      +/-   ##
==========================================
- Coverage   78.45%   78.39%   -0.07%     
==========================================
  Files        7141     7131      -10     
  Lines      315871   314944     -927     
  Branches    43462    43278     -184     
==========================================
- Hits       247831   246911     -920     
+ Misses      61721    61720       -1     
+ Partials     6319     6313       -6     

"created_by_type": CREATED_BY_TYPE_MAP["name"],
"flag": request_data["name"],
"organization_id": organization_id,
"tags": {"environment": request_data["environmentName"]},
Copy link
Member

Choose a reason for hiding this comment

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

should we standardize what we put in the tags? or does it not really matter?

i could add environment to the LD tags as well. looks like the splitio request body also has a description which i added to the LD tags intially

Copy link
Member Author

Choose a reason for hiding this comment

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

A standard tag should just be a column. Tags are meant for unstructured data that could be displayed to the user but not otherwise can not be part of the structured record.

Copy link
Member

@aliu39 aliu39 left a comment

Choose a reason for hiding this comment

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

We should keep a look out for noisy events unrelated to the flag's value (ex unleashed has a ton of "change request" events). Of course finding documentation on the schema/description of each event type would be great too, there just isn't any at https://help.split.io/ , as far as I can see 😥

Base automatically changed from mz/ld-provider to master October 28, 2024 13:30
@getsantry
Copy link
Contributor

getsantry bot commented Nov 19, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added Stale and removed Stale labels Nov 19, 2024
@getsantry
Copy link
Contributor

getsantry bot commented Dec 12, 2024

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added Stale and removed Stale labels Dec 12, 2024
@cmanallen cmanallen closed this Dec 18, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Jan 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants