Value Statement

The goal is to ensure end to end testing of the Fine Grained RBAC feature as customer would see it. The development/QE is split up between different teams - Installer, Consoler, Search and Server Foundation. The individual teams will not be focussing on this end to end experience.

Definition of Done for Engineering Story Owner (Checklist)

• Enable the TP feature like a customer would and test the happy path
• Disable TP thereafter and see if the system reverts back to its own
• Test unhappy path -
  • all clusters do not have the same OIDC set,
  • additional permissions are being granted on the managed clusters that do not exist on the hub,
  • users have never logged into the hub cluster, but they are to be assigned roles at the hub 

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.