Value Statement

Currently MulticlusterRoleAssignment does have per role assignment statuses, however the only time it will show an error is if it happens on the initial ClusterPermission update. There are many errors that can happen after ClusterPermission has been updated, such as failures with the ManifestWork, issue with ClusterPermission, etc. This ticket is to add a watch for ClusterPermission status changes, and then report relevant statuses upward to MRA role assignments.

This story is blocked by ACM-23312. Currently ClusterPermission does not report status updates per binding, or on ManifestWork failures, which is what we would need to complete this story.

Definition of Done for Engineering Story Owner (Checklist)

• Implement watch on MRA managed ClusterPermissions for status updates
• Update MRA status based ClusterPermission statuses
• End goal: if there is a failure with ClusterPermission after initial update (ManifestWork failure to create binding), then status should be updated on specific MRA role assignment status to show error.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.