Migration compatibility and tooling #208

Open
opened 2024-12-11 06:36:18 +01:00 by kamikazechaser · 4 comments

To successfully migrate, we would need to:

  • Migrate pins
  • Migrate active vouchers
  • Profile data
To successfully migrate, we would need to: - [ ] Migrate pins - [ ] Migrate active vouchers - [ ] Profile data
kamikazechaser added the
Kind/Feature
Priority
High
labels 2024-12-11 06:36:18 +01:00
kamikazechaser changed title from Migration compatibility to Migration compatibility and tooling 2024-12-11 06:36:36 +01:00
Author
Owner

The current pins are stored in hashed format. It looks like in this implementation we store them in plaintext. Is this an update we can make?

The current pins are stored in hashed format. It looks like in this implementation we store them in plaintext. Is this an update we can make?
Owner

@kamikazechaser created issue here: #209

Need more info on which hash algo was used.

@kamikazechaser created issue here: https://git.grassecon.net/urdt/ussd/issues/209 Need more info on which hash algo was used.
Owner

Migrate active vouchers

@kamikazechaser I am thinking should we just replay indexer events through term for this? Seems like the safest way.

> Migrate active vouchers @kamikazechaser I am thinking should we just replay indexer events through `term` for this? Seems like the safest way.
Owner

@kamikazechaser created issue here: #210 (comment)

@kamikazechaser created issue here: https://git.grassecon.net/urdt/ussd/issues/210#issuecomment-2976
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: urdt/ussd#208
No description provided.