Today Harness IDP workflows cannot call Harness CD APIs directly to create Services, Environments, or Pipelines. Instead, we must trigger an intermediate “orchestration” pipeline in CD, which then performs these actions, adding extra complexity, latency, and failure points.

Engineering ask: please provide first-class IDP 2.0 actions (or a supported API surface) that allow workflows to directly create/update Harness CD resources (services, environments, pipelines, config files) using a secure service identity, without needing a middle pipeline hop. This would drastically simplify IDP blueprints, improve maintainability, and make Harness IDP a true one-stop provisioning interface for CD assets.