From a344e83a39209f57ef3bf6d0be85c21bdbc86113 Mon Sep 17 00:00:00 2001 From: Rose M Koron <32436232+rkoron007@users.noreply.github.com> Date: Fri, 19 Apr 2024 14:54:38 -0700 Subject: [PATCH] Apply suggestions from code review Co-authored-by: rita <8647768+ritsok@users.noreply.github.com> --- .github/ISSUE_TEMPLATE/bug_report.yml | 2 +- .github/ISSUE_TEMPLATE/config.yml | 4 ++-- .github/ISSUE_TEMPLATE/feature_request.yml | 2 +- internal/cloud/e2e/README.md | 4 ++-- website/docs/language/style.mdx | 2 +- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 58f157712537..f580b8da43a4 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -15,7 +15,7 @@ body: For general usage questions, please see: https://www.terraform.io/community.html. ## If your issue relates to: - * **HCP Terraform or Enterprise**: please email tf-cloud@hashicorp.support or [open a new request](https://support.hashicorp.com/hc/en-us/requests/new). + * **HCP Terraform or Terraform Enterprise**: please email tf-cloud@hashicorp.support or [open a new request](https://support.hashicorp.com/hc/en-us/requests/new). * **AWS Terraform Provider**: Open an issue at [hashicorp/terraform-provider-aws](https://github.com/hashicorp/terraform-provider-aws/issues/new/choose). * **Azure Terraform Provider**: Open an issue at [hashicorp/terraform-provider-azurerm](https://github.com/hashicorp/terraform-provider-azurerm/issues/new/choose). * **Other Terraform Providers**: Please open an issue in the provider's own repository, which can be found by searching the [Terraform Registry](https://registry.terraform.io/browse/providers). diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index 4e284dfe54bd..5ad11616460d 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -3,9 +3,9 @@ blank_issues_enabled: false contact_links: - - name: HCP Terraform or Enterprise Troubleshooting and Feature Requests + - name: HCP Terraform and Terraform Enterprise Troubleshooting and Feature Requests url: https://support.hashicorp.com/hc/en-us/requests/new - about: For issues and feature requests related to the HCP Terraform/Enterprise platform, please submit a HashiCorp support request or email tf-cloud@hashicorp.support + about: For issues and feature requests related to HCP Terraform and Terraform Enterprise, please submit a HashiCorp support request or email tf-cloud@hashicorp.support - name: AWS Terraform Provider Feedback and Questions url: https://github.com/hashicorp/terraform-provider-aws about: The AWS Terraform Provider has its own repository, any provider related issues or questions should be directed there. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index c99a13d3a231..0cb1cd11ec66 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -15,7 +15,7 @@ body: For general usage questions, please see: https://www.terraform.io/community.html. ## If your feature request relates to: - * **HCP Terraform or Enterprise**: please email tf-cloud@hashicorp.support or [open a new request](https://support.hashicorp.com/hc/en-us/requests/new). + * **HCP Terraform or Terraform Enterprise**: please email tf-cloud@hashicorp.support or [open a new request](https://support.hashicorp.com/hc/en-us/requests/new). * **AWS Terraform Provider**: Open an issue at [hashicorp/terraform-provider-aws](https://github.com/hashicorp/terraform-provider-aws/issues/new/choose). * **Azure Terraform Provider**: Open an issue at [hashicorp/terraform-provider-azurerm](https://github.com/hashicorp/terraform-provider-azurerm/issues/new/choose). * **Other Terraform Providers**: Please open an issue in the provider's own repository, which can be found by searching the [Terraform Registry](https://registry.terraform.io/browse/providers). diff --git a/internal/cloud/e2e/README.md b/internal/cloud/e2e/README.md index 1892eee293f9..c8c585f5d616 100644 --- a/internal/cloud/e2e/README.md +++ b/internal/cloud/e2e/README.md @@ -10,7 +10,7 @@ Required flags external network calls. This is needed to run these tests. Without it, the tests do not run. * `TFE_TOKEN=` and `TFE_HOSTNAME=`. The helpers -for these tests require admin access to an HCP Terraform/TFE instance. +for these tests require admin access to an HCP Terraform or Terraform Enterprise instance. * `-timeout=30m`. Some of these tests take longer than the default 10m timeout for `go test`. ### Flags @@ -19,6 +19,6 @@ for these tests require admin access to an HCP Terraform/TFE instance. * Use the `-tfoutput` flag to print the terraform output to standard out. * Use `-ldflags` to change the version Prerelease to match a version available remotely. Some behaviors rely on the exact local version Terraform -being available in HCP Terraform/TFE, and manipulating the Prerelease during build is +being available in HCP Terraform or Terraform Enterprise, and manipulating the Prerelease during build is often the only way to ensure this. [(More on `-ldflags`.)](https://www.digitalocean.com/community/tutorials/using-ldflags-to-set-version-information-for-go-applications) diff --git a/website/docs/language/style.mdx b/website/docs/language/style.mdx index f217f8d73611..48b2fdc111e7 100644 --- a/website/docs/language/style.mdx +++ b/website/docs/language/style.mdx @@ -516,7 +516,7 @@ Review the [module creation recommended pattern documentation](/terraform/tutori ## Local modules -Local modules are sourced from local disk rather than a remote module registry. We recommend publishing your modules to a module registry, such as the [HCP Terraform private module registry](/terraform/cloud-docs/registry), to easily version, share, and reuse modules across your organization. If you cannot use a module registry, using local modules can simplify maintaining and updating your code. +Local modules are sourced from local disk rather than a remote module registry. We recommend publishing your modules to a module registry, such as the [HCP Terraform private registry](/terraform/cloud-docs/registry), to easily version, share, and reuse modules across your organization. If you cannot use a module registry, using local modules can simplify maintaining and updating your code. We recommend that you define child modules in the `./modules/` directory.