Story

As a RHDH user, I want to use orchestrator workflows 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, determine whether to call the scaffolder API or the Orchestrator API

• This could be handled by checking what configuration values have been set

A new configuration value for the Bulk Import plugin to determine what orchestrator workflow will be used

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

Upstream documentation updates (design docs, release notes etc)

• Any potential new requirements (Orchestrator plugin)
• An example orchestrator workflow

Technical enablement / Demo