EPIC Goal

Enable the Bulk Import plugin to automatically leverage existing Orchestrator workflows.

Background/Feature Origin

The Bulk Import plugin currently requires manual implementation to handle repository imports. Customers want to use pre-defined 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 feature aims to utilize existing infrastructure to automate and optimize bulk import operations effectively.

Why is this important?

Users could use Orchestrator workflows with flexible scenarios to make various import operations under projects.{}

User Scenarios

1. Upon repositories selection, the plugin must call an Orchestrator API to trigger the appropriate workflow.
2. Provide a Orchestrator workflow reference that handles the default behavior of adding entities
3. Documentation must be updated to explain how the platform engineer can select which template to run.

Dependencies (internal and external)

Coordination with the Frontend team is required, as these changes will necessitate either the removal or updating of existing frontend components responsible for catalog entity PR creation.

Acceptance Criteria

Release Enablement/Demo - Provide necessary release enablement details
and documents

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>

DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>

DEV - Downstream build attached to advisory: <link to errata>

QE - Test plans in Playwright: <link or reference to playwright>

QE - Automated tests merged: <link or reference to automated tests>

DOC - Downstream documentation merged: <link to meaningful PR>