-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
chore(roles): remove redundant variant from PermissionGroup #6985
base: main
Are you sure you want to change the base?
chore(roles): remove redundant variant from PermissionGroup #6985
Conversation
Changed Files
|
@@ -0,0 +1 @@ | |||
SELECT 1; |
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.
Should we replace the groups back here? If someone rolls back to older version, new variant wouldn't work.
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.
We cannot revert the groups back, this is a one time activity for renaming recon_ops
to recon_ops_manage
. Once this is done, we will lose context of which groups were recon_ops
, and that's expected since application expects recon_ops_manage
If someone rolls back to an older version of the application, it will work regardless since we've had the new variant (ReconOpsManage) for a while.
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.
But I don't see any issue in replacing either... If someone reverts to the version where ReconOpsManage
is not present, then it wouldn't work without replacing.
I would not expect anyone to do so. But, this is something I can think of which will give us advantage without any downsides...
Type of Change
Description
This removes the redundant
ReconOps
variant fromPermissionGroup
enum which is stored in DB. This was kept back in application for backwards compatibility. Migrations are added for this and this will not be needed anymore.Additional Changes
Motivation and Context
Helps in keeping a clean permission view on HS dashboard.
How did you test it?
Locally by running migrations and viewing permission view in dashboard.
Checklist
cargo +nightly fmt --all
cargo clippy