harness_update
Update existing Harness resources, including pipelines and input sets, by supplying a YAML or JSON definition or a Harness URL to auto-extract identifiers.
Instructions
Update an existing Harness resource. For pipelines/input sets: pass body as a YAML string directly (recommended for complex definitions), or use body.yamlPipeline/body.pipeline. You can pass a Harness URL to auto-extract identifiers. Response includes openInHarness link to the updated resource when applicable.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | A Harness UI URL — org, project, resource type, ID, and supported resource_scope are extracted automatically | |
| body | Yes | The updated resource definition body. For pipelines: pass a YAML string directly, or an object with yamlPipeline (YAML string) or pipeline (JSON object) | |
| org_id | No | Org identifier. Required unless a Harness URL is passed (no configured default). | |
| params | No | Additional identifiers (e.g. pipeline_id for triggers/input sets, version_label for templates). | |
| confirm | No | User-approved confirmation for medium/high-risk operations when the client cannot show a prompt. Set only with user intent; never overrides a user's decline. | |
| project_id | No | Project identifier. Required for project-scoped resources unless a Harness URL is passed (no configured default). | |
| resource_id | No | The identifier of the resource to update. Optional when url contains the resource ID. | |
| resource_type | Yes | The type of resource to update | |
| resource_scope | No | account|org|project. Omit for the resource's default scope. Never use account to skip a known org/project. Auto-detected from url. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||