From 328fb42aa48e8664e9416b98f9fff6d9a0bea900 Mon Sep 17 00:00:00 2001 From: rkoron007 Date: Tue, 7 Oct 2025 14:46:59 -0700 Subject: [PATCH 1/4] Add a note to change the tfc_hostname variable --- .../integrations/aws-service-catalog/index.mdx | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx index be4dc31fc..76de65181 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx @@ -27,6 +27,16 @@ By combining HCP Terraform with AWS Service Catalog, we’re combining a self-se ## Installation & Configuration + + + + +Set the `tfc_hostname` variable in your Terraform configuration to `app.eu.terraform.io` to use the AWS service catalog with an HCP Europe organization. + + + + + To start using this integration, you'll need to install the [AWS Service Catalog Engine for Terraform Cloud](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc) provided by HashiCorp on GitHub by following the [setup instructions](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc#getting-started) provided in the README. If you run into any setup troubles along the way, the README also includes [troubleshooting steps](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc#troubleshooting) that should help resolve common issues that you may encounter. With the engine installed, the necessary code and infrastructure to integrate the HCP Terraform engine with AWS Service Catalog will automatically be configured. The setup can be completed in just a few minutes, and it only needs to be done once. Once the setup is complete, you can immediately start using AWS Service Catalog to develop and manage AWS Service Catalog products, and make them accessible to your end users across all your accounts. From e35780ed0a2f7de86175859577fd51cd5c1bf182 Mon Sep 17 00:00:00 2001 From: rkoron007 Date: Tue, 7 Oct 2025 15:00:10 -0700 Subject: [PATCH 2/4] Add a link --- .../docs/cloud-docs/integrations/aws-service-catalog/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx index 76de65181..6d1b56d4b 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx @@ -31,7 +31,7 @@ By combining HCP Terraform with AWS Service Catalog, we’re combining a self-se -Set the `tfc_hostname` variable in your Terraform configuration to `app.eu.terraform.io` to use the AWS service catalog with an HCP Europe organization. +To use the AWS service catalog integration with an HCP Europe organization, set the example [`tfc_hostname` variable](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc/blob/main/variables.tf#L15-L19) to `app.eu.terraform.io` in your configuration. From 5f60cb2ace4a13d5e69b0a504352a583eff35ccd Mon Sep 17 00:00:00 2001 From: rkoron007 Date: Wed, 8 Oct 2025 09:20:27 -0700 Subject: [PATCH 3/4] Fix stack command --- content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx b/content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx index 73464cdb8..6912a8c66 100644 --- a/content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/stacks/create.mdx @@ -58,7 +58,7 @@ Stacks live alongside workspaces in an HCP Terraform project. To create a new St 1. Run the `terraform stacks create` command, replacing the placeholders with your organization name, project name, and desired Stack name: ```shell-session - $ terraform stacks create -organization -project -stack-name + $ terraform stacks create -organization-name -project-name -stack-name ``` A Stack name must be unique within the project and can include letters, numbers, dashes (`-`), and underscores (`_`). We recommend using 90 characters or less for the name of your Stack. From 039bc566b89e735448bc02ad9bb4f0540d847173 Mon Sep 17 00:00:00 2001 From: rkoron007 Date: Wed, 8 Oct 2025 09:21:55 -0700 Subject: [PATCH 4/4] Remove extra file --- .../integrations/aws-service-catalog/index.mdx | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx index 6d1b56d4b..be4dc31fc 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/aws-service-catalog/index.mdx @@ -27,16 +27,6 @@ By combining HCP Terraform with AWS Service Catalog, we’re combining a self-se ## Installation & Configuration - - - - -To use the AWS service catalog integration with an HCP Europe organization, set the example [`tfc_hostname` variable](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc/blob/main/variables.tf#L15-L19) to `app.eu.terraform.io` in your configuration. - - - - - To start using this integration, you'll need to install the [AWS Service Catalog Engine for Terraform Cloud](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc) provided by HashiCorp on GitHub by following the [setup instructions](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc#getting-started) provided in the README. If you run into any setup troubles along the way, the README also includes [troubleshooting steps](https://github.com/hashicorp/aws-service-catalog-engine-for-tfc#troubleshooting) that should help resolve common issues that you may encounter. With the engine installed, the necessary code and infrastructure to integrate the HCP Terraform engine with AWS Service Catalog will automatically be configured. The setup can be completed in just a few minutes, and it only needs to be done once. Once the setup is complete, you can immediately start using AWS Service Catalog to develop and manage AWS Service Catalog products, and make them accessible to your end users across all your accounts.