Migration compatibility and tooling #208
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
Activity
Doing
Activity
Proposal
Activity
QA
Runner
AT
Runner
CLI
Runner
HTTP
cleanup
devops
documentation
easypeasy
exchange
l8ter
legacy
meta
migration
optimization
privilege
refactor
smell
support
tooling
ux
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: urdt/ussd#208
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To successfully migrate, we would need to:
Migration compatibilityto Migration compatibility and toolingThe 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?
@kamikazechaser created issue here: #209
Need more info on which hash algo was used.
@kamikazechaser I am thinking should we just replay indexer events through
term
for this? Seems like the safest way.@kamikazechaser created issue here: #210 (comment)