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

Payments: migrate from Wise borderless-accounts to newer alternatives #1755

Open
jayaddison opened this issue Jul 6, 2024 · 1 comment
Open
Assignees
Labels
dependencies Pull requests that update a dependency file 🧹Housekeeping python Pull requests that update Python code
Milestone

Comments

@jayaddison
Copy link
Contributor

We have a few references in the codebase to Wise Borderless Accounts; there are newer/preferred alternatives available in the Wise API for use instead.

If possible it'd be nice to rename some of our model database columns accordingly at the same time. I think we could do that by adding a second column of the same name / constraints, and performing an UPDATE during the upgrade/downgrade database migrations. Yes, theoretically an alias column would work too, but I think it may be simpler for the bidirectional migrations simply to duplicate the column temporarily.

An upgrade of the pywisetransfer dependency will be required alongside these changes.

@jayaddison jayaddison added 🧹Housekeeping dependencies Pull requests that update a dependency file python Pull requests that update Python code labels Jul 6, 2024
@jayaddison jayaddison added this to the Post-2024 milestone Jul 6, 2024
@jayaddison jayaddison self-assigned this Jul 6, 2024
@marksteward
Copy link
Member

Probably worth waiting until after we wipe down the DB (should be in the next month), We can wipe all the migrations at the same time, as that's well overdue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file 🧹Housekeeping python Pull requests that update Python code
Projects
None yet
Development

No branches or pull requests

2 participants