-
Bug
-
Resolution: Done
-
Normal
-
1.6.0
-
1
-
False
-
-
False
-
-
Bug Fix
-
Done
-
-
Description of problem:
If the ArgoCD plugin or Quay plugin has been enabled in the rhdh instance and also added to the app-config so that the permission will be discoverable, it does not show up in the UI.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
- Enable the ArgoCD or Quay plugin
- Add the ArgoCD or Quay plugin to the list of `pluginsWithPermissions`
- Enable the rbac frontend plugin
- Give yourself admin access
- Navigate to the admin page of the rbac plugin
- Attempt to create a role and permission using the `argocd.view.read` or `quay.view.read` permission
- Notice that argocd or quay is not an option for a plugin
Actual results:
The inability to create a role with the argocd and quay plugin permission from the frontend
Expected results:
The ability to create a role with the argocd or quay plugin permission from the frontend
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Additional info (Such as Logs, Screenshots, etc):
There is a workaround in which you have to call the rbac backend plugin api directly or declare through the use of the CSV file to add the `argocd.view.read` permission. There are also backend plugins ArgoCD and Quay that fix this issue but they are currently not part of preinstalled plugins in rhdh.