From 5e83d1ae0b600c2a8af723d13d56012526de815a Mon Sep 17 00:00:00 2001 From: Yevgeniy Brikman Date: Fri, 15 Apr 2022 14:03:02 +0100 Subject: [PATCH 1/2] Add missing link to production framework The production framework guide promises a closer look at app & infra pipelines later in the guide... But there is no such content later. Therefore, I've replaced that promise with a link to a blog post we wrote before that has exactly this content. --- .../ingredients/ci-cd-pipeline/ci-cd-features.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md index 7146a73162..65fa98f1f6 100644 --- a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md +++ b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md @@ -30,7 +30,7 @@ Depending on what you're deploying, you'll want your tools to support different ## Application and infrastructure code -The CI / CD pipeline needs to work with both application code (e.g., a web service written in Java, Ruby, Go, or Python) and infrastructure code (e.g., Terraform, CloudFormation). These two types of pipelines have slightly different requirements. You'll see examples of this later in this guide. +The CI / CD pipeline needs to work with both application code (e.g., a web service written in Java, Ruby, Go, or Python) and infrastructure code (e.g., Terraform, CloudFormation). These two types of pipelines have slightly different requirements. For a detailed side-by-side look at application and infrastructure pipelines, check out [How to Use Terraform as a Team](https://blog.gruntwork.io/how-to-use-terraform-as-a-team-251bc1104973). ## Example From 1110d49daf78e2f3b725cfb62a0a25ebd5b20b3b Mon Sep 17 00:00:00 2001 From: "docs-sourcer[bot]" <99042413+docs-sourcer[bot]@users.noreply.github.com> Date: Fri, 15 Apr 2022 13:03:08 +0000 Subject: [PATCH 2/2] Updated `_docs-sources` with this contribution and regenerated output. --- .../ingredients/ci-cd-pipeline/ci-cd-features.md | 2 +- .../ingredients/ci-cd-pipeline/ci-cd-features.md | 5 ++++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/_docs-sources/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md b/_docs-sources/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md index 3e5c672d9e..58450f4997 100644 --- a/_docs-sources/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md +++ b/_docs-sources/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md @@ -30,7 +30,7 @@ Depending on what you're deploying, you'll want your tools to support different ## Application and infrastructure code -The CI / CD pipeline needs to work with both application code (e.g., a web service written in Java, Ruby, Go, or Python) and infrastructure code (e.g., Terraform, CloudFormation). These two types of pipelines have slightly different requirements. You'll see examples of this later in this guide. +The CI / CD pipeline needs to work with both application code (e.g., a web service written in Java, Ruby, Go, or Python) and infrastructure code (e.g., Terraform, CloudFormation). These two types of pipelines have slightly different requirements. For a detailed side-by-side look at application and infrastructure pipelines, check out [How to Use Terraform as a Team](https://blog.gruntwork.io/how-to-use-terraform-as-a-team-251bc1104973). ## Example diff --git a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md index 65fa98f1f6..cf600970ce 100644 --- a/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md +++ b/docs/guides/production-framework/ingredients/ci-cd-pipeline/ci-cd-features.md @@ -39,5 +39,8 @@ AWS](https://docs.gruntwork.io/docs/guides/build-it-yourself/landing-zone/).