You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs-sources/guides/build-it-yourself/pipelines/index.md
+2-76Lines changed: 2 additions & 76 deletions
Original file line number
Diff line number
Diff line change
@@ -3,86 +3,12 @@ sidebar_label: What you’ll learn in this guide
3
3
pagination_label: Set Up an Infrastructure CI/CD Pipeline
4
4
---
5
5
6
-
import { CardList } from "/src/components/CardGroup"
7
-
8
6
# Set Up an Infrastructure CI/CD Pipeline
9
7
10
8
:::info
11
9
12
-
This document is an excellent resource for understanding the problem space of CI/CD and the design choices that Gruntwork Pipelines makes.
10
+
We are in the process of updating this document.
13
11
14
-
If you are looking to get hands-on with Gruntwork Pipelines and deploy it yourself, see [the official examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines)
12
+
In the meantime, if you are a Gruntwork customer looking to get hands-on with Gruntwork Pipelines, see [the official examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines)
15
13
16
14
:::
17
-
18
-
## Overview
19
-
20
-
This is a comprehensive guide explaining the problem space of CI/CD, its threat vectors, and the design decisions that Gruntwork Pipelines
21
-
makes in order to keep your sensitive credentials secure.
22
-
23
-
## What this guide will not cover
24
-
25
-
This guide is not hands-on! If you're looking to explore and play around with Gruntwork Pipelines, you should instead view and deploy [our official
26
-
examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines).
27
-
28
-
CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There
29
-
are several items that this guide will not cover, including:
30
-
31
-
<divclassName="dlist">
32
-
33
-
#### A pipeline for setting up new environments
34
-
35
-
This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set
36
-
up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve
37
-
the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically
38
-
require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in
39
-
a reasonable fashion that still respects the threat model we cover here.
40
-
41
-
#### Automated testing and feature toggling strategies for infrastructure code
42
-
43
-
An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give
44
-
you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially
45
-
integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new
46
-
developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure
47
-
code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our
48
-
talk
49
-
[Automated
50
-
testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post
Copy file name to clipboardExpand all lines: docs/guides/build-it-yourself/pipelines/index.md
+3-77Lines changed: 3 additions & 77 deletions
Original file line number
Diff line number
Diff line change
@@ -3,94 +3,20 @@ sidebar_label: What you’ll learn in this guide
3
3
pagination_label: Set Up an Infrastructure CI/CD Pipeline
4
4
---
5
5
6
-
import { CardList } from "/src/components/CardGroup"
7
-
8
6
# Set Up an Infrastructure CI/CD Pipeline
9
7
10
8
:::info
11
9
12
-
This document is an excellent resource for understanding the problem space of CI/CD and the design choices that Gruntwork Pipelines makes.
10
+
We are in the process of updating this document.
13
11
14
-
If you are looking to get hands-on with Gruntwork Pipelines and deploy it yourself, see [the official examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines)
12
+
In the meantime, if you are a Gruntwork customer looking to get hands-on with Gruntwork Pipelines, see [the official examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines)
15
13
16
14
:::
17
15
18
-
## Overview
19
-
20
-
This is a comprehensive guide explaining the problem space of CI/CD, its threat vectors, and the design decisions that Gruntwork Pipelines
21
-
makes in order to keep your sensitive credentials secure.
22
-
23
-
## What this guide will not cover
24
-
25
-
This guide is not hands-on! If you're looking to explore and play around with Gruntwork Pipelines, you should instead view and deploy [our official
26
-
examples in our service catalog](https://github.com/gruntwork-io/terraform-aws-service-catalog/tree/master/examples/for-production/gruntwork-pipelines).
27
-
28
-
CI/CD for infrastructure code is a large topic and a single guide cannot cover everything. There
29
-
are several items that this guide will not cover, including:
30
-
31
-
<divclassName="dlist">
32
-
33
-
#### A pipeline for setting up new environments
34
-
35
-
This guide will focus on a CI/CD workflow for making changes to infrastructure in an environment that is already set
36
-
up. In other words, the design and implementation of the pipeline covered in this guide intentionally does not solve
37
-
the use case of infrastructure code for setting up an environment from scratch. Setting up new environments typically
38
-
require complex deployment orders and permissions modeling that complicate the task. This makes it hard to automate in
39
-
a reasonable fashion that still respects the threat model we cover here.
40
-
41
-
#### Automated testing and feature toggling strategies for infrastructure code
42
-
43
-
An important factor of CI/CD pipelines is the existence of automated testing and feature toggles. Automated tests give
44
-
you confidence in the code before it is deployed to production. Similarly, feature toggles allow you to partially
45
-
integrate and deploy code for a feature without enabling it. By doing so, you are able to continuously integrate new
46
-
developments over time. This guide will briefly introduce automated testing and feature toggles for infrastructure
47
-
code, but will not do a deep dive on the subject. You can learn more about best practices for automated testing in our
48
-
talk
49
-
[Automated
50
-
testing for Terraform, Docker, Packer, Kubernetes, and More](https://blog.gruntwork.io/new-talk-automated-testing-for-terraform-docker-packer-kubernetes-and-more-cba312171aa6) and blog post
0 commit comments