Value Statement

Come up with a design proposal that solves these problems:

For Green field deployments, customers will have the ACM GH first, and then they will create the ACM hubs from there - as we are seeing for TELCO POCs etc. If a customer defines user or a type of user to have access to certain clusters in GH, we should not need them to define it again in ACM hub. This information should be propagated. 

For brown field deployments, customers will have the ACMs first, and then they will create the GH from there - as we are seeing for enterprise customers etc. ACM hubs will have the RBAC permission for a  user or a type of user to have access to certain clusters in that ACM hub. How can we propagate this information to the GH so that the customer does not have to define it again in GH.

Definition of Done for Engineering Story Owner (Checklist)

• ...

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.