Skip to content

Commit

Permalink
Add missing link to production framework (#284)
Browse files Browse the repository at this point in the history
* 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>
  • Loading branch information
brikis98 and docs-sourcer[bot] authored Apr 20, 2022
1 parent 0a191db commit 3ac8c58
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 3 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand All @@ -39,5 +39,8 @@ AWS](https://docs.gruntwork.io/docs/guides/build-it-yourself/landing-zone/).


<!-- ##DOCS-SOURCER-START
{"sourcePlugin":"local-copier","hash":"be59b854b7665f188f7878b449f542e7"}
{
"sourcePlugin": "local-copier",
"hash": "52893974c9e95ad383ac61f7e2d718e5"
}
##DOCS-SOURCER-END -->

0 comments on commit 3ac8c58

Please sign in to comment.