Skip to content

chore(roles): remove redundant variant from PermissionGroup#6985

Merged
likhinbopanna merged 5 commits intomainfrom
6983-chore-remove-redundant-variants-from-permissiongroup
Feb 6, 2025
Merged

chore(roles): remove redundant variant from PermissionGroup#6985
likhinbopanna merged 5 commits intomainfrom
6983-chore-remove-redundant-variants-from-permissiongroup

Conversation

@kashif-m
Copy link
Contributor

@kashif-m kashif-m commented Jan 3, 2025

Type of Change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Dependency updates
  • Documentation
  • CI/CD

Description

This removes the redundant ReconOps variant from PermissionGroup 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

  • This PR modifies the API contract
  • This PR modifies the database schema
  • This PR modifies application configuration/environment variables

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

  • I formatted the code cargo +nightly fmt --all
  • I addressed lints thrown by cargo clippy
  • I reviewed the submitted code
  • I added unit tests for my changes where possible

@kashif-m kashif-m self-assigned this Jan 3, 2025
@kashif-m kashif-m requested a review from a team as a code owner January 3, 2025 10:45
@kashif-m kashif-m linked an issue Jan 3, 2025 that may be closed by this pull request
2 tasks
@semanticdiff-com
Copy link

semanticdiff-com bot commented Jan 3, 2025

@hyperswitch-bot hyperswitch-bot bot added the M-database-changes Metadata: This PR involves database schema changes label Jan 3, 2025
@kashif-m kashif-m requested a review from a team as a code owner January 3, 2025 12:24
@@ -0,0 +1 @@
SELECT 1;
Copy link
Contributor

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.

Copy link
Contributor Author

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.

Copy link
Contributor

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...

@Gnanasundari24 Gnanasundari24 added this pull request to the merge queue Jan 27, 2025
@Gnanasundari24 Gnanasundari24 removed this pull request from the merge queue due to a manual request Jan 27, 2025
@Gnanasundari24 Gnanasundari24 added this pull request to the merge queue Jan 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 29, 2025
@likhinbopanna likhinbopanna added this pull request to the merge queue Jan 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 29, 2025
@likhinbopanna likhinbopanna added this pull request to the merge queue Jan 29, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 29, 2025
@pixincreate pixincreate added this pull request to the merge queue Jan 30, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 30, 2025
@pixincreate pixincreate added this pull request to the merge queue Jan 30, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 30, 2025
@kashif-m kashif-m disabled auto-merge February 3, 2025 06:33
@Gnanasundari24 Gnanasundari24 added this pull request to the merge queue Feb 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks Feb 3, 2025
@Gnanasundari24 Gnanasundari24 added this pull request to the merge queue Feb 3, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 3, 2025
@likhinbopanna likhinbopanna added this pull request to the merge queue Feb 6, 2025
Merged via the queue into main with commit 775dcc5 Feb 6, 2025
17 of 20 checks passed
@likhinbopanna likhinbopanna deleted the 6983-chore-remove-redundant-variants-from-permissiongroup branch February 6, 2025 14:29
pixincreate added a commit that referenced this pull request Feb 7, 2025
…unt-configurable

* 'main' of github.com:juspay/hyperswitch: (37 commits)
  refactor(router): add display_name field to connector feature api  (#7121)
  ci(cypress): Add Tests for Customer Deletion and Psync flows (#7158)
  feat(connector): [DataTrans] ADD 3DS Flow (#6026)
  chore(version): 2025.02.07.0
  chore(connectors): [fiuu] update pm_filters for apple pay and google pay (#7182)
  feat(router): add `organization_id` in authentication table and add it in authentication events (#7168)
  fix(dashboard_metadata): mask `poc_email` and `data_value` for DashboardMetadata (#7130)
  feat(core): Add support for v2 payments get intent using merchant reference id (#7123)
  refactor(customer): return redacted customer instead of error (#7122)
  fix(connector): handle unexpected error response from bluesnap connector (#7120)
  feat(routing): Contract based routing integration  (#6761)
  refactor(dynamic_fields): dynamic fields for Adyen and Stripe, renaming klarnaCheckout, WASM for KlarnaCheckout (#7015)
  feat(connector): [COINGATE] Add Template PR  (#7052)
  chore(roles): remove redundant variant from PermissionGroup (#6985)
  refactor(router): store `network_transaction_id` for `off_session` payments irrespective of the `is_connector_agnostic_mit_enabled` config (#7083)
  chore(connector): [Fiuu] log keys in the PSync response (#7189)
  ci(cypress): fix nmi and paypal (#7173)
  chore(version): 2025.02.06.0
  chore(postman): update Postman collection files
  feat(connector): [Deutschebank] Add Access Token Error struct (#7127)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

M-database-changes Metadata: This PR involves database schema changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CHORE] remove redundant variants from PermissionGroup

4 participants