From 3ac8c58a2f7d359c9d808f9379c32fdf1b11d97d Mon Sep 17 00:00:00 2001 From: Yevgeniy Brikman Date: Wed, 20 Apr 2022 12:48:36 +0100 Subject: [PATCH] Add missing link to production framework (#284) * 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. * Updated `_docs-sources` with this contribution and regenerated output. Co-authored-by: docs-sourcer[bot] <99042413+docs-sourcer[bot]@users.noreply.github.com> --- .../ingredients/ci-cd-pipeline/ci-cd-features.md | 2 +- .../ingredients/ci-cd-pipeline/ci-cd-features.md | 7 +++++-- 2 files changed, 6 insertions(+), 3 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 3e5c672d9..58450f499 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 7146a7316..cf600970c 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 @@ -39,5 +39,8 @@ AWS](https://docs.gruntwork.io/docs/guides/build-it-yourself/landing-zone/).