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.

Sign up for GitHub

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

Jump to bottom

Migration - Entitlements #2709

Closed
j1010001 opened this issue Aug 9, 2023 · 4 comments
Closed

Migration - Entitlements #2709

j1010001 opened this issue Aug 9, 2023 · 4 comments
Assignees
@dsainati1
Labels
Feature
Milestone
C1.0-Launch-M3

Comments

@j1010001
Copy link
Member

j1010001 commented Aug 9, 2023

No description provided.

@j1010001 j1010001 mentioned this issue Aug 9, 2023
Open
This was referenced Aug 9, 2023
Closed
Closed
@j1010001 j1010001 added this to the OKR-23-Q4 milestone Oct 17, 2023
@j1010001 j1010001 changed the title Entitlements migration Migration - Entitlements Oct 17, 2023
@j1010001 j1010001 modified the milestones: OKR-23-Q4, C1.0-Launch-M2 Nov 14, 2023
@j1010001
Copy link
Member Author

Remaining decision to make:
How do we deal with contracts that are not updated in time for migration during network upgrade ?
The way this migration is implemented depends on the decision - we could do some kind of lazy-migration at runtime.

@dsainati1
Copy link
Contributor

#2705 and #2705 implement most of this, the remaining work here is just to hook up this functionality to the new migration framework, and pull in contracts as necessary to typecheck the new values.

@dsainati1 dsainati1 mentioned this issue Nov 21, 2023
Merged
6 tasks
@turbolent
Copy link
Member

@dsainati1 Do you think we can close this know as done, or is there anything left to be done here?

@dsainati1
Copy link
Contributor

Yeah! I’ll close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dsainati1 dsainati1

Labels
Feature
Projects
None yet
Milestone
C1.0-Launch-M3
Development

No branches or pull requests
3 participants
@turbolent @dsainati1 @j1010001