Story

As a RHDH user, I want to use scaffolder templates to define the pre-ingestion process for my repositories identified within the Bulk Import plugin.

Background

The Bulk Import plugin currently requires manual implementation to handle repository imports. Customers want to use pre-defined Backstage templates and Orchestrator workflows that facilitate various operations, such as creating repositories across multiple Git platforms, requesting approvals, and publishing code or configurations to repositories. By integrating the Bulk Import plugin with these existing templates and workflows, we can reduce redundancy, and enhance user efficiency. This story aims to utilize existing infrastructure to automate and optimize bulk import operations effectively.

Dependencies and Blockers

QE impacted work

Documentation impacted work

Acceptance Criteria

At the time of import, instead of directly creating a GitHub PR, we will instead call the scaffolder API

A new configuration value for the Bulk Import plugin to determine what software template will be used

• At the moment, we are only concerned with giving users the ability to use a single software template

Upstream documentation updates (design docs, release notes etc)

• New requirements for the configuration of the plugin
• An example software template for the Bulk Import to use
• The new requirements of needing to enable at a minimum the github scaffolder backend module (additional scaffolder backend modules would be required for any other scaffolder actions the user decided to incorporate into their software template)

Technical enablement / Demo