Currently, Harness IDP 2.0 workflows do not support direct HTTP or REST API calls from within workflow steps. This limitation significantly restricts the ability to perform dynamic or programmatic actions (such as creating pipelines, environments, or services) directly from the IDP workflow.

To work around this, we’ve been forced to create a separate admin pipeline in Harness CD, which acts as a proxy execution layer. The IDP workflow triggers this CD pipeline via API to perform the actual create/update actions. While this workaround functions, it introduces unnecessary indirection, complexity, and maintenance overhead especially when scaling to multiple automation workflows.

Expected Outcome:

Ability to perform CRUD operations on Harness entities (pipelines, environments, services) directly from IDP workflows.

Simplified architecture: no need for proxy CD pipelines.

more seamless user experience.

Closer alignment of Harness IDP 2.0 with modern platform engineering and automation us