Skip to content

Include how to use service catalog without for-production example #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Parent: Fixing sample usage module path for VPC deployment config
merged 3 commits into from
Jan 26, 2023
Merged

Include how to use service catalog without for-production example #533

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
67a60a3
Update overview.md
rhoboat Sep 23, 2022
3c52e6c
Update overview.md
rhoboat Sep 23, 2022
5c6237a
Updated `_docs-sources` with this contribution and regenerated output.
docs-sourcer[bot] Sep 23, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion _docs-sources/reference/services/intro/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

Expand Down
8 changes: 6 additions & 2 deletions docs/reference/services/intro/overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.

Expand Down Expand Up @@ -96,6 +100,6 @@ Makes sure to ALWAYS read the release notes and migration instructions (if any)
<!-- ##DOCS-SOURCER-START
{
"sourcePlugin": "local-copier",
"hash": "5eb1606803f10d39a682642586a222a0"
"hash": "750a36ba2c3ba2455d2eba763802109d"
}
##DOCS-SOURCER-END -->