Story

As a user of RHDH, I want to be able to create permissions for the Tekton plugin through the use of the RBAC UI so that users can have limited access to the Tekton 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 Tekton plugin does not have a backend plugin of its own, instead it relies on the Upstream Backstage Kubernetes backend plugin. As such we have current work that involves adding permissions to the Kubernetes backend plugin. When merged, we can replace the old Tekton plugin permission with the newly create Kubernetes plugin permissions.

Dependencies and Blockers

Another team owns the Tekton plugins.

Waiting on Backstage to review and merge changes to the Kubernetes plugins.

QE impacted work

Documentation impacted work

Acceptance Criteria

upstream documentation updates (design docs, release notes etc)

Technical enablement / Demo