diff --git a/_docs-sources/reference/services/intro/overview.md b/_docs-sources/reference/services/intro/overview.md index 3fb9412d22..1dc21197c7 100644 --- a/_docs-sources/reference/services/intro/overview.md +++ b/_docs-sources/reference/services/intro/overview.md @@ -63,7 +63,11 @@ The code in the `terraform-aws-service-catalog` repo is organized into three pri integrated tech stack on top of the Gruntwork Service Catalog. To keep the code DRY and manage dependencies between modules, the code is deployed using [Terragrunt](https://terragrunt.gruntwork.io/). However, Terragrunt is NOT required to use the Gruntwork Service Catalog: you can alternatively use vanilla Terraform or Terraform - Cloud / Enterprise, as described later in these docs. + Cloud / Enterprise, as described [here](https://docs.gruntwork.io/reference/services/intro/deploy-new-infrastructure#how-to-deploy-terraform-code-from-the-service-catalog). + + 1. Not all modules have a `for-production` example, but you can still create a production-grade configuration by + using the template provided in this discussion question, [How do I use the modules in terraform-aws-service-catalog + if there is no example?](https://github.com/gruntwork-io/knowledge-base/discussions/360#discussioncomment-25705480). 1. `test`: Automated tests for the code in `modules` and `examples`. diff --git a/docs/reference/services/intro/overview.md b/docs/reference/services/intro/overview.md index 2e23c3e39e..8f6c2fee88 100644 --- a/docs/reference/services/intro/overview.md +++ b/docs/reference/services/intro/overview.md @@ -63,7 +63,11 @@ The code in the `terraform-aws-service-catalog` repo is organized into three pri integrated tech stack on top of the Gruntwork Service Catalog. To keep the code DRY and manage dependencies between modules, the code is deployed using [Terragrunt](https://terragrunt.gruntwork.io/). However, Terragrunt is NOT required to use the Gruntwork Service Catalog: you can alternatively use vanilla Terraform or Terraform - Cloud / Enterprise, as described later in these docs. + Cloud / Enterprise, as described [here](https://docs.gruntwork.io/reference/services/intro/deploy-new-infrastructure#how-to-deploy-terraform-code-from-the-service-catalog). + + 1. Not all modules have a `for-production` example, but you can still create a production-grade configuration by + using the template provided in this discussion question, [How do I use the modules in terraform-aws-service-catalog + if there is no example?](https://github.com/gruntwork-io/knowledge-base/discussions/360#discussioncomment-25705480). 1. `test`: Automated tests for the code in `modules` and `examples`. @@ -96,6 +100,6 @@ Makes sure to ALWAYS read the release notes and migration instructions (if any)