-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[HOLD for payment 2023-12-07] [HOLD for payment 2023-10-13] [HOLD for payment 2023-07-14] Onyx migration for personalDetails changes #21454
Comments
This comment was marked as duplicate.
This comment was marked as duplicate.
@s77rt if you want, you can C+ all of them. There will probably be at least 3 or 4 PRs. |
@puneetlath That would be great |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.35-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-07-10. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.37-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-07-14. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
Planning to help with |
@Beamanator We have PR for that already #22432 |
@Beamanator is working on the back-end that should unblock the last couple pieces. Hopefully we're very close to the finish line here 🤞🏾 |
Getting closer! |
Next (last?) PR is here: #31664 |
I believe we're officially done with this now that the last PR was merged 🎉 @Beamanator @s77rt do you agree that we're done? Or are we still missing something? |
I thinkkkk yes we can finally close this one out! (if payment is complete) |
What about this one? |
Hmm, I can't remember what I meant by that. Is there a way we can know that the migration doesn't need to run and skip it that y'all can think of? |
haha fair point - i don't think we'd have any way of knowing that it already ran unless we set some kind of NVP, but we'd have to have it run for every device where you had logged in to your account - so I don't think we need to do that now, we may need to if we start running too many migrations that end up taking a long time or something? |
Agree ^ I think we are good to close for now |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.5-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2023-12-07. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
Ok, I count a total of 7 PRs which would be $3500. Does that sound right? |
I found 6 PRs. All are pretty minimal, it should be $250 each. Total: $1500 |
Ok that sounds good. Thank you for being so honest and straightforward. Offer here: https://www.upwork.com/nx/wm/offer/27918877 |
Accepted! Thanks! |
Alright paid. Closing this out! |
Part of "Secure Logins in NewDot" Project
As part of this project, we started sending new data to Onyx that was accountID-based (e.g. personalDetailsList, participantAccountIDs, etc). We did not stop sending the old data, but we will be soon.
As a cleanup item, we should add an Onyx migration for two reasons:
We should have this ready to go-live after https://github.com/Expensify/Expensify/issues/294647 is done.
This migration will be handled in stages:
Before updating the back-end:
Once back-end has been updated to stop sending email-based data:
The text was updated successfully, but these errors were encountered: