Skip to content

ACM-24275 and ACM-24267 - Implemented global role logic and MRA creation logic fix#5024

Merged
openshift-merge-bot[bot] merged 2 commits intostolostron:mainfrom
mshort55:ACM-24275
Sep 23, 2025
Merged

ACM-24275 and ACM-24267 - Implemented global role logic and MRA creation logic fix#5024
openshift-merge-bot[bot] merged 2 commits intostolostron:mainfrom
mshort55:ACM-24275

Conversation

@mshort55
Copy link
Copy Markdown
Contributor

@mshort55 mshort55 commented Sep 23, 2025

📝 Summary

Implemented global role RA creation and fixed MRA creation logic to choose existing MRA for user if exists.

Ticket Summary (Title):
RBAC UI Implementation - Propogate to all (global role) during role assignment creation
RBAC UI Implementation - update MRA client for single user MRA creation/edit

Ticket Link:
https://issues.redhat.com/browse/ACM-24275
https://issues.redhat.com/browse/ACM-24267

Type of Change:

  • 🐞 Bug Fix
  • ✨ Feature
  • 🔧 Refactor
  • 💸 Tech Debt
  • 🧪 Test-related
  • 📄 Docs

✅ Checklist

General

  • PR title follows the convention (e.g. ACM-12340 Fix bug with...)
  • Code builds and runs locally without errors
  • No console logs, commented-out code, or unnecessary files
  • All commits are meaningful and well-labeled
  • All new display strings are externalized for localization (English only)
  • (Nice to have) JSDoc comments added for new functions and interfaces

If Feature

  • UI/UX reviewed (if applicable)
  • All acceptance criteria met
  • Unit test coverage added or updated
  • Relevant documentation or comments included

If Bugfix

  • Root cause and fix summary are documented in the ticket (for future reference / errata)
  • Fix tested thoroughly and resolves the issue
  • Test(s) added to prevent regression

🗒️ Notes for Reviewers

…ssignment creation. Fixed MRA creation logic in client to patch instead of create if user MRA exists already..

Signed-off-by: Matthew Short <mshort@redhat.com>
Signed-off-by: Matthew Short <mshort@redhat.com>
@mshort55
Copy link
Copy Markdown
Contributor Author

/retest

@mshort55
Copy link
Copy Markdown
Contributor Author

/assign @oksanabaza @kurwang
Please review, thanks.

@mshort55
Copy link
Copy Markdown
Contributor Author

/retest

1 similar comment
@mshort55
Copy link
Copy Markdown
Contributor Author

/retest

@oksanabaza
Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm label Sep 23, 2025
scope: {
...prevData.scope,
clusterNames: roleAssignmentData.allClusterNames,
namespaces: undefined,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine with undefined but would it be better to say like includes all namespaces or like all namespaces?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Undefined is actually intentional here. If namespaces is undefined, that means that targetNamespaces does not get added on the MRA RoleAssignment (this creates a ClusterRoleBinding when targetNamespaces is not present in the spec). This is actually what we want here, if all is selected, for namespaces to be empty or undefined. On the UI itself, empty or undefined namespaces does get translated and shows "All Namespaces".

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah i see i agree! that clears it up thanks!

@mshort55
Copy link
Copy Markdown
Contributor Author

/hold

@KevinFCormier
Copy link
Copy Markdown
Contributor

/approve

@kurwang
Copy link
Copy Markdown
Contributor

kurwang commented Sep 23, 2025

/lgtm

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Sep 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: KevinFCormier, kurwang, mshort55, oksanabaza

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mshort55
Copy link
Copy Markdown
Contributor Author

/unhold

@sonarqubecloud
Copy link
Copy Markdown

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants