Is this you? As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.
Claim your profile
Articles by Yevgeniy Brikman
The future of Terraform must be open
Our plan and pledge to keep Terraform open source On August 10, 2023, HashiCorp announced that after ~9 years of Terraform being open source under the MPL v2 license, they were suddenly switching it to a non open source BSL v1.1 license. We believe the BSL license is a poison pill for Terraform which threatens the entire community and ecosystem, and in this blog post, we’ll introduce OpenTF, our plan for keeping Terraform open source—forever.
Terraform: Up and Running, 3rd Edition
Book description Terraform has become a key player in the DevOps world for defining, launching, and managing infrastructure as code (IaC) across a variety of cloud and virtualization platforms, including AWS, Google Cloud, Azure, and more. This hands-on third edition, expanded and thoroughly updated for version 1.0 and beyond, shows you the fastest way to get up and running with Terraform.
The Docker, Kubernetes, Terraform, and AWS crash course series
Ramp up on DevOps tools in minutes via a series of lightning quick, hands-on crash courses where you learn by doing. It’s well-known that Docker, Kubernetes, Terraform, and AWS are all the rage these days, forming the core of many modern DevOps toolsets. What’s less well-known is that many developers have no idea what these technologies really are—and they are too afraid to ask. This used to be me.
Introducing git-xargs: an open source tool to update multiple GitHub repos
Today we’re open sourcing git-xargs, a command-line tool (CLI) for making updates across multiple Github repositories with a single command. You give git-xargs a script to run and a list of repos, and it checks out each repo, runs your scripts against it, commits any changes, and opens pull requests with the results. At the end of each run, you get a detailed report on exactly what happened with each repo: For example, have you ever needed to add a particular file across many repos at once?
Automated Testing for Terraform, Docker, Packer, Kubernetes, and More
Transcript Brikman: This talk is called "How to Test Infrastructure Code." I will go through some automated testing practices that we found for tools like Terraform, Docker, Packer, Kubernetes. There will be a lot of code, so get ready to read code, this is hands-on. I'll try to run some of the code, we'll see how that goes.
Terraform: Up & Running
Writing Infrastructure as Code By Yevgeniy Brikman Publisher: O'Reilly Media Release Date: June 2019 Pages: 350 Read on O'Reilly Online Learning with a 10-day trial Start your free trial now Buy on Amazon Where’s the cart? Now you can get everything with O'Reilly Online Learning. To purchase books, visit Amazon or your favorite retailer. Questions?
5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code
5 Lessons Learned From Writing Over 300,000 Lines of Infrastructure Code A concise masterclass on how to write infrastructure code This October, I gave a talk at HashiConf 2018 where I shared 5 key lessons we learned at Gruntwork while creating and maintaining a library of over 300,000 lines of infrastructure code that’s used in production by hundreds of companies.
How to design a product at a startup
For someone browsing the web, Google is a text box and a page of results, and not the bots that crawl the web, the algorithm to rank pages, or the hundreds of thousands of servers in multiple data centers around the world. For someone who needs a ride, Uber is a button on their phone they can push to order a car, and not the real-time dispatch system, the payment processing systems, or all the effort that goes into recruiting drivers and fighting with regulators.
Open sourcing Terratest: a swiss army knife for testing infrastructure code
Open sourcing Terratest: a swiss army knife for testing infrastructure code Tools to test Terraform, Packer, Docker, AWS, and much more Infrastructure as code (IaC) tools such as Terraform, Packer, and Docker offer a number of advantages: you can automate your entire provisioning and deployment process, you can store the state of your infrastructure in code (instead of a sysadmin’s head), you can use version control to track the history of how your infrastructure has changed, and so on.
Why we use Terraform and not Chef, Puppet, Ansible, SaltStack, or CloudFormation
Update, November 17, 2016: We took this blog post series, expanded it, and turned it into a book called Terraform: Up & Running! Update, July 8, 2019: We’ve updated this blog post series for Terraform 0.12 and released the 2nd edition of Terraform: Up & Running! This is Part 1 of the Comprehensive Guide to Terraform series. In the intro to the series, we discussed why every company should be using infrastructure-as-code (IAC).
Why use Terraform?
Software isn’t done when the code is working on your computer. It’s not done when the tests pass. And it’s not done when someone gives you a "ship it" on a code review. Software isn’t done until you deliver it to the user. Software delivery consists of all the work you need to do to make the code available to a customer, such as running that code on production servers, making the code resilient to outages and traffic spikes, and protecting the code from attackers.
A Minimum Viable Product Is Not a Product, It’s a Process
“You know that old saw about a plane flying from California to Hawaii being off course 99% of the time—but constantly correcting? The same is true of successful startups—except they may start out heading toward Alaska.” —-Evan Williams It’s the same story again and again. First, a team comes up with an idea. Next, they build a minimum viable product (MVP) as a proof of concept, spending a lot of time arguing about which features to include or exclude from the MVP.
アジャイルな開発には安全性が不可欠 : 現実世界の安全機構との3つのアナロジー
仮に、高速道路の自動車をより速く走らせることがあなたの務めだとします。もしあなたが、ドライバー全員にただ「アクセルを思いきり踏むように」と言ったら、一体どうなるでしょうか？ 結果は明らかに、大惨事となるでしょう。それなのに、ソフトウェアの構築を速めようとする時に、多くの開発者がまさにそんな態度を取っているのです。その理由として持ち出されるのは、以下のようなことです。 「本当にアジャイルに進めたいので、デザインやドキュメントには時間をかけられない」 「これは本番環境にすぐ反映しなきゃいけないから、テストを書く時間はない」 「何もかも自動化する時間はなかったので、コードのデプロイは手作業でやる」 自動車が高速道路を高速で走るには、安全性が欠かせません。より速く走るためには、ブレーキやシートベルト、エアバッグといった、いざという時にドライバーを危険から守るための安全機構が不可欠です。...
Hello, Startup - O'Reilly Media
The tools you need to get started with data, from basic statistics to complex modeling and large-scale analytics. This book is the "Hello, World" tutorial for building products, technologies, and teams in a startup environment.
Show More
loading
Actions
Is this you?
As a journalist, you can create a free Muck Rack account to customize your profile, list your contact preferences, and upload a portfolio of your best work.Get in touch with Yevgeniy
Contact Yevgeniy, search articles and posts on X, monitor coverage, and track replies from one place.
Learn more about Muck Rack