Skip to content

Commit 4393d68

Browse files
authored
Update README.md
1 parent 46a2a6d commit 4393d68

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,15 +7,15 @@
77
<a href="https://diggerhq.gitbook.io/digger-docs/">Docs</a>
88
</h2>
99

10-
Digger is Github Action that runs Terraform `plan` and `apply` with PR-level locks
10+
Digger runs Terraform jobs in the CI/CD system you already have, such as Github Actions.
1111

12-
Unlike Terraform Cloud or Spacelift, terraform jobs run natively in your Github Actions - no need to share sensitive data with another CI system
12+
CI/CD for Terraform is [not easy](https://itnext.io/pains-in-terraform-collaboration-249a56b4534e). This is why Terraform Cloud, Spacelift and Atlantis are essentially standalone full-stack CI/CD systems.
1313

14-
Unlike Atlantis, there's no need to deploy and maintain a backend service.
14+
But why have 2 CI systems? Why not reuse the existing CI infrastructure? Digger does just that.
1515

16-
<img width="693" alt="Screenshot 2023-02-24 at 19 52 12" src="https://user-images.githubusercontent.com/1280498/221277610-368ae950-6319-4bf3-9df2-ca75ca5a05f9.png">
16+
With Digger terraform jobs natively in your CI runners. It takes care of locks, state, outputs etc.
1717

18-
Demo video: https://www.loom.com/share/e201e639a73941e0b5508710377a6106
18+
[Demo video](https://www.loom.com/share/e201e639a73941e0b5508710377a6106)
1919

2020
## Features
2121
- code-level locks - only 1 open PR can run plan / apply. This avoids conflicts

0 commit comments

Comments
 (0)