S
Satisfied Lark
Description:
The Harness IACM Module Registry provides an automated Onboarding Pipeline capability, which allows platform teams to automatically generate testing, validation, and publishing pipelines when adding new IaC modules. However, the Provider Registry currently lacks this functionality, requiring engineers to manually build, configure, and maintain individual pipeline definitions to publish and validate custom or private IaC providers.
We request native support for Default Onboarding Pipelines within the IACM Provider Registry. Adding a new cloud or infrastructure provider should trigger or allow auto-generation of a standard onboarding pipeline to handle security scanning, binary validation, documentation compilation, and version publishing.
Business Impact:
  1. Operational Efficiency: Streamlines the onboarding process for custom and private providers, eliminating repetitive manual pipeline construction by platform engineers.
  2. Standardized Security & Compliance: Guarantees that every provider published to the internal registry undergoes automated security checks, signature verifications, and compliance scans before availability.
  3. Feature Parity: Delivers consistency across registry workflows in the IACM platform by aligning Provider Registry governance directly with existing Module Registry capabilities.