From 1fc608720decf52a2ca710663c08eeab2180104b Mon Sep 17 00:00:00 2001 From: Yordan Halachev Date: Mon, 15 Sep 2025 14:07:49 +0300 Subject: [PATCH 1/2] Update run-tasks-integration.mdx --- .../cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx b/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx index 2215ebccea..3e222dc556 100644 --- a/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/api-docs/run-tasks/run-tasks-integration.mdx @@ -157,7 +157,7 @@ You can send outcomes with a status of `running`, `passed`, or `failed`, but it ### Request Body -The PATCH request submits a JSON object with the following properties as a request payload. This payload is also described in the [JSON schema for run task results](https://github.com/hashicorp/web-unified-docs/content/terraform-docs-common/public/schema/run-tasks/runtask-result.json). +The PATCH request submits a JSON object with the following properties as a request payload. This payload is also described in the [JSON schema for run task results](https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/public/schema/run-tasks/runtask-result.json). | Key path | Type | Description | | ----------------------------- | ------ | --------------------------------------------------------------------------------- | From 05a87e93b8448d5b1faad24dcaff93f17a74026d Mon Sep 17 00:00:00 2001 From: Yordan Halachev Date: Mon, 15 Sep 2025 14:17:33 +0300 Subject: [PATCH 2/2] Update index.mdx --- .../docs/cloud-docs/integrations/run-tasks/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx index c78a6d602d..c157402592 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/run-tasks/index.mdx @@ -85,7 +85,7 @@ Here's what the data flow looks like: ![Screenshot: a diagram of the user and data flow for an HCP Terraform run task](/img/docs/terraform-cloud-run-tasks-diagram.png) -Refer to the [run task integration API](/terraform/cloud-docs/api-docs/run-tasks/run-tasks-integration#structured-results) for the exact payload specifications, and the [JSON schema for run task results](https://github.com/hashicorp/web-unified-docs/content/terraform-docs-common/public/schema/run-tasks/runtask-result.json) for code generation and payload validation. +Refer to the [run task integration API](/terraform/cloud-docs/api-docs/run-tasks/run-tasks-integration#structured-results) for the exact payload specifications, and the [JSON schema for run task results](https://github.com/hashicorp/web-unified-docs/blob/main/content/terraform-docs-common/public/schema/run-tasks/runtask-result.json) for code generation and payload validation. ## Securing your Run Task