Why you should take care of Infrastructure Driftby@driftctl
335 reads
335 reads

Why you should take care of Infrastructure Drift

by @driftctl4mDecember 14th, 2020
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

DevOps teams are keenly aware of the issue and actively looking for solutions. API-driven drift happens when an update from an application or script calling a cloud provider API (or a Terraform provider) directly impacts your actual infras. The most common causes of drift are linked with process or workflow issues, like manual changes in a cloud console not being transposed as code, or changes applied to some environment but not propagated to others. While drift mostly causes additional work, it also triggers severe security issues too.

Company Mentioned

Mention Thumbnail
featured image - Why you should take care of Infrastructure Drift
@driftctl HackerNoon profile picture
@driftctl

@driftctl

@driftctl

driftctl is a free and open-source CLI that tracks and warns of infrastructure drift

Share Your Thoughts

About Author

@driftctl HackerNoon profile picture
@driftctl@driftctl
driftctl is a free and open-source CLI that tracks and warns of infrastructure drift

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
L O A D I N G
. . . comments & more!