The team decided developing driftctl in the open was the best way to continue gathering feedback, prioritizing their focus, and iterating on the problem. The CloudSkiff team talked to over 100 IaC users, they quickly realized that drift - the changes that occur outside the IaC workflow after an environment is running - was a major source of pain for many people. The only thing more terrifying than a fast-moving broken thing is a slow-moving broken thing that you can't get anyone to pay attention to because what harm could that iceberg do… - Yvonne Lam November 9, 2020 IaC drift might be one of those slow-moving broken things, but as the tweet states, “The only thing more terrifying than a fast-moving broken thing is a slow-moving broken thing that you can’t get anyone to pay attention to because what harm could that iceberg do…” So they were all too familiar with the “emergency” changes and tweaked settings that led the true state of their infrastructure to differ from the desired state.Ī tweet shared by the CloudSkiff team pointed out the impact of fast versus slow-moving broken things. The team were all experienced cloud infrastructure managers, either as developers deploying to cloud resources or as part of a larger DevOps oriented organization managing large production systems.
#CODEVISION ARM CODE#
Who is CloudSkiff?ĬloudSkiff started up in July 2019 in Paris, France with ideas about how they could help users manage their infrastructure as code (IaC) projects. I wanted to share with you why we’re excited about the addition of this fantastic group of people to Snyk, and our plans for the future of Snyk Infrastructure as Code (Snyk IaC), as well as our commitment to keeping driftctl open source.Įditor’s note: The acquisition of Cloudskiff closed on October 29, 2021. We are thrilled to welcome the team at CloudSkiff to Snyk! Many of you may be more familiar with driftctl, the open source project started by the CloudSkiff team.
0 kommentar(er)
