-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
5
-
True
-
-
False
-
-
Once ready, we should update
AccountRolesARNsSection.jsx#L216-216
to:
const accountRolesARNs = get(getAWSAccountRolesARNsResponse, 'data', []).filter((arn) => // TODO: restore when managed policies are in place // isHypershiftSelected ? (arn.hcpManagedPolicies && arn.managedPolicies) : (!arn.hcpManagedPolicies && arn.managedPolicies) , isHypershiftSelected ? ... : (!arn.hcpManagedPolicies && arn.managedPolicies), // '...' meaning whatever is there keep );
Note:
// isHypershiftSelected ? (arn.hcpManagedPolicies && arn.managedPolicies) : (!arn.hcpManagedPolicies && arn.managedPolicies) ,
Is the complete, correct logic when managed-policies are supported in both rosa classic, and rosa hosted, based on past comments:
Per usage of backend `hcpManagedPolicies` and `managedPolicies` fields: * For hypershift managed policies both fields are true * For rosa classic unmanaged both are false * (out of scope) For rosa classic managed policies (the epic is on hold right now) managedPolicies:true and hcpManagedPolicies:false