-
Bug
-
Resolution: Unresolved
-
Normal
-
ACM 2.14.0
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
ACM Console Train 30 - 2
-
Moderate
-
None
Description of problem:
Currently, the 'Create application" button is can only enabled when the permission for the AppSub CR is added to the Role of the User.
As an effort to include RBAC testing for ApplicationSets, we want to ensure the 'Create application' button is always clickable for users and implement logic to dynamically enable or disable the individual options (e.g., Argo CD ApplicationSet, Subscription) presented in its dropdown menu based on relevant permissions.
Version-Release number of selected component (if applicable):
latest-2.14
How reproducible:
Always
Steps to Reproduce:
- Enable appset creation through
kind: Role metadata: name: appset-edit namespace: openshift-gitops rules: - apiGroups: ["argoproj.io"] resources: ["applicationsets"] verbs: ["get", "list", "watch", "create", "update", "patch"]
Actual results:
Create Application button is disabled
Expected results:
Create application should be enabled and the subsequent individual options should have the pull and push model enabled and appsub disabled.
Additional info:
- is related to
-
ACM-14544 ACM a ClusterRole to enable fine-grained RBAC for ApplicationSets should not depend on AppSub
-
- New
-