-
Notifications
You must be signed in to change notification settings - Fork 0
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
HPC-9944: Add v4 models to Role
and WorkflowRole
tables
#212
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please review the comment! Other than that is looking fine
export type WorkflowRoleId = Brand< | ||
number, | ||
{ readonly s: unique symbol }, | ||
'workflowRole.id' | ||
>; | ||
|
||
export const WORKFLOW_ROLE_ID = brandedType<number, WorkflowRoleId>(t.number); | ||
|
||
// export const PERMITTED_ACTION_IDS = t.union([ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this unused code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason why v4 models don't have these tables is that they are considered legacy and should not be used in any new code. Since you need to write temporary admin command, which must fix corrupt legacy data, I think you can use legacy models for that purpose.
In related hpc_service PR, if you can write all code using v4 models and only use legacy models for legacy tables, that would be best. But, if combining models isn't possible in some place, it's fine to use legacy models there too, since it is a temporary thing, fixing legacy stuff.
No longer needed. |
No description provided.