Chapter 7. Known issues

A conditional alias that uses $ownerRefs doesn’t work.

There is no workaround.

Only the first 20 repositories (in alphabetical order) can be displayed at most on the Bulk Import Added Repositories page. Also, the count of Added Repositories displayed might be wrong. In future releases, we plan to address this with proper pagination. Meanwhile, as a workaround, searching would still work against all Added Repositories. So you can still search any Added Repository and get it listed on the table.

Some permissions that only have frontend plugins will not show up in the UI due to a requirement of needing a backend plugin to expose the permission framework’s wellknow endpoint. As a workaround, you can either apply these permissions through the use of the CSV file or by directly calling the REST API of the RBAC backend plugin. Known plugins affected are Topology topology.view.read, Tekton tekton.view.read, ArgoCD argocd.view.read, and Quay quay.view.read.

Repositories might be added to Developer Hub from various sources (like statically in an app-config file or dynamically when enabling GitHub discovery). By design, the bulk import plugin will only track repositories that are accessible from the configured GitHub integrations. When both the Bulk Import and the GitHub Discovery plugins are enabled, the repositories the latter discovers might be listed in the Bulk Import pages. However, attempting to delete a repository added by the discovery plugin from the Bulk Import Jobs may have no effect, as any entities registered from this repository might still be present in the Developer Hub catalog. There is unfortunately no known workaround yet.