sundowndev
/
driftctl
mirror of https://github.com/sundowndev/driftctl.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Detect, track and alert on infrastructure drift
1,446 Commits
2 Branches
0 Tags
7.9 MiB
Go 98.2%
HCL 1.5%
Shell 0.2%
CSS 0.1%
 
 
 
 
Go to file
Raphaël 75cd450a63
Merge pull request #905 from cloudskiff/fix/listedTypeAlerts 
Include resource ID in scanning errors to ignore a particular resource
 		2021-08-04 11:16:04 +02:00
.circleci remove useless go mod download from make test 2021-07-30 17:58:46 +02:00
.github chore: add need-triage label to bug issues 2021-06-23 10:47:29 +02:00
build
…
docs Remove duplicate doc files, update root README and re-organize docs folder 2021-03-03 11:41:28 +01:00
logger log everything as trace 2021-02-11 14:17:06 +01:00
mocks Move driftignore init outside driftctl 2021-07-26 14:27:07 +02:00
pkg refactor: fix lint errors 2021-08-04 11:08:08 +02:00
scripts ci: add parallelism to goreleaser release command 2021-07-27 15:16:52 +02:00
sentry ignore usage errors from sentry capture 2021-02-09 22:19:24 +01:00
test add retry for destroy on some acceptancy tests 2021-07-30 17:33:41 +02:00
.all-contributorsrc docs: update .all-contributorsrc [skip ci] 2021-06-16 08:12:56 +00:00
.dockerignore Ignore .terraform folders from docker context 2021-03-10 17:04:55 +01:00
.editorconfig Change json identation 2021-04-29 16:36:32 +02:00
.gitignore chore: fix lint errors 2021-07-22 17:33:49 +02:00
.go-version Update go version and add make deps to fix Ci issues 2021-03-30 14:56:20 +02:00
.golangci.yml Remove reference used in loops 2021-02-04 22:45:10 +01:00
.goreleaser.yml chore: fix lint errors 2021-07-22 17:33:49 +02:00
.mockery.yaml remove testonly from mockery config 2021-02-16 18:05:18 +01:00
CONTRIBUTORS.md docs: update CONTRIBUTORS.md [skip ci] 2021-06-16 08:12:55 +00:00
Dockerfile Fix docker build 2021-07-27 16:16:04 +02:00
LICENSE.md
…
Makefile remove useless go mod download from make test 2021-07-30 17:58:46 +02:00
README.md updated link to discord 2021-06-17 14:29:49 +02:00
ROADMAP.md initial ROADMAP.md, after team meeting 2021-01-29 16:32:26 +01:00
codecov.yml Change range of coverage colors 2021-03-03 12:28:01 +01:00
go.mod Bump aws-sdk 2021-06-28 16:38:49 +02:00
go.sum remove useless go mod download from make test 2021-07-30 17:58:46 +02:00
goland_watchers.xml Use printer to not break output isolation 2021-03-15 12:03:35 +01:00
main.go fix: sentry report message 2021-04-20 16:00:39 +02:00
test.sh enforce AZ to something predictible for acc tests 2021-07-30 09:29:33 +02:00

README.md

driftctl

Measures infrastructure as code coverage, and tracks infrastructure drift.
IaC: Terraform, Cloud providers: AWS, GitHub (Azure and GCP on the roadmap for 2021).
⚠️ This tool is still in beta state and will evolve in the future with potential breaking changes ⚠️

Packaging status Packaging status

Why driftctl ?

Infrastructure drift is a blind spot and a source of potential security issues. Drift can have multiple causes: from team members creating or updating infrastructure through the web console without backporting changes to Terraform, to unexpected actions from authenticated apps and services.

You can't efficiently improve what you don't track. We track coverage for unit tests, why not infrastructure as code coverage?

Spot discrepancies as they happen: driftctl is a free and open-source CLI that warns of infrastructure drifts and fills in the missing piece in your DevSecOps toolbox.

Features

  • Scan cloud provider and map resources with IaC code
  • Analyze diffs, and warn about drift and unwanted unmanaged resources
  • Allow users to ignore resources
  • Multiple output formats

Get Started

Documentation

Installation

Discord

Contribute

To learn more about compiling driftctl and contributing, please refer to the contribution guidelines and the contributing guide for technical details.

This project follows the all-contributors specification and is brought to you by these awesome contributors.

Build with ❤️️ from 🇫🇷 🇯🇵 🇬🇷 🇸🇪 🇺🇸 🇷🇪

Helping you get started

We have 30 min slots for 1:1 tech discussions and overviews twice a day to help you get started and collect users feedback.

Feel free to book a slot.