サクサク読めて、アプリ限定の機能も多数!
トップへ戻る
都知事選
blog.gruntwork.io
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. Why
[Update, Aug 15, 2023] Please see our new blog post for more detailed thoughts and our plan for the future: The future of Terraform must be open—our plan and pledge to keep Terraform open source. On Thursday, August 10, 2023, HashiCorp announced that it was switching Terraform from the MPL v2 license to a “Business Source License” (BSL). In this blog post, we’d like to address how this impacts Gru
I’m happy to announce the beta release of Gruntwork Patcher, a tool to automatically keep your infrastructure code up-to-date, even with breaking changes! This first release of Patcher allows Gruntwork Compliance customers to upgrade their Reference Architecture from version 1.4 to 1.5 of the CIS AWS Foundations Benchmark, pulling in over 200 changes, and fixing 3 breaking changes—automatically. I
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. While everyone around me was throwing around buzzwords like containerization, orchestration, IaC, and EC2, I had no
One of the most common questions we get about using Terraform to manage infrastructure as code is how to handle secrets such as passwords, API keys, and other sensitive data. For example, here’s a snippet of Terraform code that can be used to deploy MySQL using Amazon RDS: resource "aws_db_instance" "example" { engine = "mysql" engine_version = "5.7" instance_class = "db.t2.micro" name = "example"
In late 2016, we released the Comprehensive Guide to Terraform blog post series. It got so much attention (the series is now approaching 2 million views!) that a few months later, in early 2017, we turned it into a book, Terraform: Up & Running. It’s remarkable just how much has changed in the two years since then: 4 major Terraform releases, a language change (HCL to HCL2), a revamp of Terraform
The second reason is that building production-grade infrastructure (as in, the type of infrastructure you’d bet your company on) involves a thousand little details. The vast majority of developers don’t know what those details are, so when you’re estimating a project, you usually forget about number of critical—and time consuming—details. To avoid this issue, every time you go to work on a new pie
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. But there’s a catch: maintaining a large cod
Building reusable rockets is hard. Building reusable Terraform code is not. Image by SpaceX.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! Update, Sep 28, 2022: We’ve updated this blog
Bulkheads in the USS South Dakota. Terraform state benefits from “bulkheads” too. Image from Wikipedia.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! Update, Sep 28, 2022: We’ve update
Why we use Terraform and not Chef, Puppet, Ansible, Pulumi, 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! Update, Sep 28, 2022: We’ve updated this blog post series f
Terraform tips & tricks: loops, if-statements, and gotchas Image by Florian RichterUpdate, 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! Update, Sep 28, 2022: We’ve updated this blog post ser
このページを最初にブックマークしてみませんか?
『blog.gruntwork.io』の新着エントリーを見る
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く