-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
migration: backfill apitoken last characters #63342
Conversation
This PR has a migration; here is the generated SQL for --
-- MIGRATION NOW PERFORMS OPERATION THAT CANNOT BE WRITTEN AS SQL:
-- Raw Python operation
-- |
e95805a
to
c9bb0ac
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #63342 +/- ##
===========================================
+ Coverage 56.54% 81.34% +24.80%
===========================================
Files 5196 5208 +12
Lines 230738 231097 +359
Branches 39867 39934 +67
===========================================
+ Hits 130460 187993 +57533
+ Misses 96256 37325 -58931
- Partials 4022 5779 +1757 |
78fa9d6
to
32ee72c
Compare
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.
Looks good to me.
32ee72c
to
496a112
Compare
This PR has a migration; here is the generated SQL for --
-- MIGRATION NOW PERFORMS OPERATION THAT CANNOT BE WRITTEN AS SQL:
-- Raw Python operation
-- |
Backfills the `token_last_characters` column on existing `ApiToken` entries. As of #62972, new `ApiToken` entries are being created with this column already populated with the correct values. This backfill will only impact old tokens created prior. Tracking Issue: #58918 Related RFC: getsentry/rfcs#32
Backfills the
token_last_characters
column on existingApiToken
s.As of #62972, new
ApiToken
s are being created with this column already populated with the correct values. This backfill will only impact old tokens created prior.Tracking Issue: #58918
Related RFC: getsentry/rfcs#32