Story

As a user of RHDH, I want to be able to create permissions for the Red Hat ArgoCD plugin through the use of the RBAC UI so that users can have limited access to the Red Hat ArgoCD plugin.

Background

Today, there are a number of plugins that have implemented permissions that are unable to be viewed from within the RBAC UI. This is because they are either missing the permission declaration through the use of passing them to the `createPermissionIntegrationRouter` in their respective backend or they do not have a backend plugin at all. These plugins include: Topology, Tekton, Quay, and Red Hat ArgoCD.

The Red Hat ArgoCD plugin does not have a backend plugin of its own, instead it relies on the RoadieHQ ArgoCD backend plugin. We have a couple of options for how we wish to solve this problem.

The first potential solution is we could create our own dedicated Red Hat ArgoCD backend plugin that just exposes the necessary routes that are needed for the frontend plugin. We could then use the `createPermissionIntegrationRouter` and pass the Red Hat ArgoCD permission to secure these routes.

Or we could contribute these permissions to the RoadieHQ ArgoCD backend plugin. This would require us to make a common plugin (if they do not already have one) and add the permissions to this common plugin. Then we just expose them with `createPermissionIntegrationRouter`. As a courtesy, we should try to aim to add these permissions to their frontend plugin.

Dependencies and Blockers

Another team owns the Red Hat ArgoCD plugins.

If going with the second option, we will be dependent on RoadieHQ to accept the changes that we make.

QE impacted work

Documentation impacted work

Acceptance Criteria

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo