Sunday, December 3, 2023
HomeBig DataFingers On Tech: Infrastructure as Code

Fingers On Tech: Infrastructure as Code

Infrastructure as Code (IaC) is the administration of infrastructure (networks, digital machines, load balancers, and connection topology) by way of machine-readable definition information, quite than a bodily {hardware} configuration. GigaOm Analyst Michael Levan is at the moment conducting analysis on IaC testing, an rising sector that brings the advantages of software program testing to the infrastructure administration house.

IaC testing is a younger area, however Levan was intrigued on the maturity he noticed from a particular answer, BridgeCrew Checkov, which he describes as a pacesetter within the house. In a latest video, Levan walks viewers by way of the answer, which incorporates a UI for admins to view the outcomes of various exams, as effectively a command line interface to run exams and think about outcomes. He additionally explores points and priorities that IT determination makers ought to contemplate when evaluating IaC options.

Levan says two approaches to IaC testing are flourishing—static code evaluation for IaC and Coverage as Code.

“It’s going to be all about want. Some organizations could need some static code evaluation so that they know what the code will do and the way it will work together with methods earlier than it runs,” he says. “Different organizations will need particular insurance policies in place for the Infrastructure as Code from a safety and compliance perspective.”

As a result of the house is so new, Levan says it’s essential for the engineering lead to purchase a product that matches particular wants and might deal with the inevitable shifts that may occur over the subsequent few years. He additionally notes that whereas there’s a distinct distinction between IaC and coverage as code, the strains have gotten more and more blurred. In the end, he says, it’s essential to keep in mind that everybody working an engineering division or writing code understands that code is code—and all code must be examined.

“It doesn’t matter if it’s utility code or not, it have to be examined to make sure that when the code runs, everybody has an understanding of what it’s doing, that bugs are discovered early on, and that iterations may be made to make it extra environment friendly.”

View Michael Levan’s Stroll-Via of Bridgecrew Checkov



Please enter your comment!
Please enter your name here

Most Popular

Recent Comments