-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
chore(superuser): use option for read-write instead of FF #70083
Conversation
and ( | ||
options.get("superuser.read-write.ga-rollout") | ||
or features.has("auth:enterprise-superuser-read-write", actor=user) | ||
) |
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.
will be replacing logic like this with just the option later
if not ( | ||
features.has("auth:enterprise-superuser-read-write", actor=request.user) | ||
or options.get("superuser.read-write.ga-rollout") | ||
): |
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.
this is the only other code change besides adding the option, everything else is modifying test decorators
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #70083 +/- ##
===========================================
+ Coverage 62.92% 79.83% +16.90%
===========================================
Files 6496 6502 +6
Lines 288948 289236 +288
Branches 49777 49810 +33
===========================================
+ Hits 181821 230907 +49086
+ Misses 106710 57918 -48792
+ Partials 417 411 -6
|
Part 1 of replacing the superuser read-write feature flag with an option. There's code in getsentry that is using the flag, so we can't completely remove it yet.
The flag is not currently turned on, so using an OR for either the option or the flag for the logic is fine. This will be temporary.