Chapter 2. Bulk importing GitHub repositories Important These features are for Technology Preview only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Red Hat Developer Hub can automate GitHub repositories onboarding and track their import status. 2.1. Enabling and giving access to the Bulk Import feature You can enable the Bulk Import feature for users and give them the necessary permissions to access it. Prerequisites You have configured GitHub integration . Procedure The Bulk Import plugins are installed but disabled by default. To enable the ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import-backend-dynamic and ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import plugins, edit your dynamic-plugins.yaml with the following content: dynamic-plugins.yaml fragment plugins: - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import-backend-dynamic disabled: false - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import disabled: false See Installing and viewing dynamic plugins . Configure the required bulk.import RBAC permission for the users who are not administrators as follows: rbac-policy.csv fragment p, role:default/bulk-import, bulk.import, use, allow g, user:default/ <your_user> , role:default/bulk-import Note that only Developer Hub administrators or users with the bulk.import permission can use the Bulk Import feature. See Permission policies in Red Hat Developer Hub . Verification The sidebar displays a Bulk Import option. The Bulk Import page shows a list of Added Repositories . 2.2. Importing multiple GitHub repositories In Red Hat Developer Hub, you can select your GitHub repositories and automate their onboarding to the Developer Hub catalog. Prerequisites You have enabled the Bulk Import feature and gave access to it . Procedure Click Bulk Import in the left sidebar. Click the Add button in the top-right corner to see the list of all repositories accessible from the configured GitHub integrations. From the Repositories view, you can select any repository, or search for any accessible repositories. For each repository selected, a catalog-info.yaml is generated. From the Organizations view, you can select any organization by clicking Select in the third column. This option allows you to select one or more repositories from the selected organization. Click Preview file to view or edit the details of the pull request for each repository. Review the pull request description and the catalog-info.yaml file content. Optional: when the repository has a .github/CODEOWNERS file, you can select the Use CODEOWNERS file as Entity Owner checkbox to use it, rather than having the content-info.yaml contain a specific entity owner. Click Save . Click Create pull requests . At this point, a set of dry-run checks runs against the selected repositories to ensure they meet the requirements for import, such as: Verifying that there is no entity in the Developer Hub catalog with the name specified in the repository catalog-info.yaml Verifying that the repository is not empty Verifying that the repository contains a .github/CODEOWNERS file if the Use CODEOWNERS file as Entity Owner checkbox is selected for that repository If any errors occur, the pull requests are not created, and you see a Failed to create PR error message detailing the issues. To view more details about the reasons, click Edit . If there are no errors, the pull requests are created, and you are redirected to the list of added repositories. Review and merge each pull request that creates a catalog-info.yml file. Verification The Added repositories list displays the repositories you imported, each with an appropriate status: either Waiting for approval or Added . For each Waiting for approval import job listed, there is a corresponding pull request adding the catalog-info.yaml file in the corresponding repository. 2.3. Managing the added repositories You can oversee and manage the repositories that are imported to the Developer Hub. Prerequisites You have imported GitHub repositories . Procedure Click Bulk Import in the left sidebar to display all the current repositories that are being tracked as Import jobs, along with their status. Added The repository is added to the Developer Hub catalog after the import pull request is merged or if the repository already contained a catalog-info.yaml file during the bulk import. Note that it may take a few minutes for the entities to be available in the catalog. Waiting for approval There is an open pull request adding a catalog-info.yaml file to the repository. You can: Click the pencil icon on the right to see details about the pull request or edit the pull request content right from Developer Hub. Delete the Import job, this action closes the import PR as well. To transition the Import job to the Added state, merge the import pull request from the Git repository. Empty Developer Hub is unable to determine the import job status because the repository is imported from other sources but does not have a catalog-info.yaml file and lacks any import pull request adding it. Note After an import pull request is merged, the import status is marked as Added in the list of Added Repositories, but it might take a few seconds for the corresponding entities to appear in the Developer Hub Catalog. A location added through other sources (like statically in an app-config.yaml file, dynamically when enabling GitHub discovery , or registered manually using the "Register an existing component" page) might show up in the Bulk Import list of Added Repositories if the following conditions are met: The target repository is accessible from the configured GitHub integrations. The location URL points to a catalog-info.yaml file at the root of the repository default branch. 2.4. Understanding the Bulk Import audit Logs The Bulk Import backend plugin adds the following events to the Developer Hub audit logs. See Audit Logs in Red Hat Developer Hub for more information on how to configure and view audit logs. Bulk Import Events : BulkImportUnknownEndpoint Tracks requests to unknown endpoints. BulkImportPing Tracks GET requests to the /ping endpoint, which allows us to make sure the bulk import backend is up and running. BulkImportFindAllOrganizations Tracks GET requests to the /organizations endpoint, which returns the list of organizations accessible from all configured GitHub Integrations. BulkImportFindRepositoriesByOrganization Tracks GET requests to the /organizations/:orgName/repositories endpoint, which returns the list of repositories for the specified organization (accessible from any of the configured GitHub Integrations). BulkImportFindAllRepositories Tracks GET requests to the /repositories endpoint, which returns the list of repositories accessible from all configured GitHub Integrations. BulkImportFindAllImports Tracks GET requests to the /imports endpoint, which returns the list of existing import jobs along with their statuses. BulkImportCreateImportJobs Tracks POST requests to the /imports endpoint, which allows to submit requests to bulk-import one or many repositories into the Developer Hub catalog, by eventually creating import pull requests in the target repositories. BulkImportFindImportStatusByRepo Tracks GET requests to the /import/by-repo endpoint, which fetches details about the import job for the specified repository. BulkImportDeleteImportByRepo Tracks DELETE requests to the /import/by-repo endpoint, which deletes any existing import job for the specified repository, by closing any open import pull request that could have been created. Example bulk import audit logs { "actor": { "actorId": "user:default/myuser", "hostname": "localhost", "ip": "::1", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36" }, "eventName": "BulkImportFindAllOrganizations", "isAuditLog": true, "level": "info", "message": "'get /organizations' endpoint hit by user:default/myuser", "meta": {}, "plugin": "bulk-import", "request": { "body": {}, "method": "GET", "params": {}, "query": { "pagePerIntegration": "1", "sizePerIntegration": "5" }, "url": "/api/bulk-import/organizations?pagePerIntegration=1&sizePerIntegration=5" }, "response": { "status": 200 }, "service": "backstage", "stage": "completion", "status": "succeeded", "timestamp": "2024-08-26 16:41:02" }

Commands:
plugins: - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import-backend-dynamic disabled: false - package: ./dynamic-plugins/dist/janus-idp-backstage-plugin-bulk-import disabled: false
p, role:default/bulk-import, bulk.import, use, allow g, user:default/ <your_user> , role:default/bulk-import
{ "actor": { "actorId": "user:default/myuser", "hostname": "localhost", "ip": "::1", "userAgent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36" }, "eventName": "BulkImportFindAllOrganizations", "isAuditLog": true, "level": "info", "message": "'get /organizations' endpoint hit by user:default/myuser", "meta": {}, "plugin": "bulk-import", "request": { "body": {}, "method": "GET", "params": {}, "query": { "pagePerIntegration": "1", "sizePerIntegration": "5" }, "url": "/api/bulk-import/organizations?pagePerIntegration=1&sizePerIntegration=5" }, "response": { "status": 200 }, "service": "backstage", "stage": "completion", "status": "succeeded", "timestamp": "2024-08-26 16:41:02" }