Gruntwork

Gruntwork's February Newsletter is out! We've got an alpha of Terragrunt Stacks, EKS Auto Mode support, Database support in Terratest, new Cloudfront Modules and more! https://lnkd.in/gDG8uyKY

We're running an Infrastructure as Code survey and would love your response!! It's a quick (10 question) survey and you'll get a chance to win $20! https://lnkd.in/gtXsRrwC We are looking to learn more about how engineers are interacting with Infrastructure as Code tools, the technologies they prefer, and the services they rely on. As a thank you for participating, we'll be randomly selecting 10 respondents to send $20 gift cards to. Share with your friends!

Ever get tired of waiting for "terraform plan/apply" to finish? Us too. At Gruntwork we work with customers with truly massive Terraform/OpenTofu estates and work with them to break down their "terraliths" into more manageable components. There are four main topologies we work with: The All In One —?aka Mega Modules or a Terralith Workspaces —?A single unit with multiple versions of state Multi-Unit?— Multiple, independently maintained units Stack —?Orchestrate multi-unit deployments as a single, versioned entity We just published a blog post discussing the tradeoffs of these topologies and some guides on how to implement each, check it out! https://lnkd.in/gN3XdphP

Gruntwork is and always has been a 100% remote company, and over the years we've learned a few lessons about running efficient engineering meetings. Some key ideas: - Collect information in parallel - Store topics in a permanent database to be revisited with timestamped updates - Use synchronous time for high-bandwidth conversations, such as conflict resolution or information-gathering We've modified stand-up so much that we use new name: Café What do you think or your team's stand-ups? Would you try a Café? https://lnkd.in/gy6A6-_H

It's been a year since OpenTofu has been in GA. It's time to make the switch. * OpenTofu has maintained 100% backwards compatibility with Terraform, and Terraform providers -- your existing code WILL work * OpenTofu has proven an ability to build hard things that Terraform refused to - provider for_each, state encryption, early evaluation etc. * OpenTofu has proven its community driven, working on a roadmap driven by the community, governed by a diverse group of companies with no ability or interest in locking down the product. * Terraform has already started moving in a more proprietary direction, features like Terraform Stacks are now Hashicorp enterprise exclusive - and the ambiguity around the BSL has only increased since the switch What are you waiting for? https://lnkd.in/g9ZGSViU

At Gruntwork, we occasionally get asked "OpenTofu/Terraform has just launched this new exciting feature. What does this mean for Terragrunt?" We've discussed this internally, and decided that the best way to address this is to write out our response as a blog post that folks can reference. After giving the post a read, consider sharing it if you hear a similar question out in the wild! https://lnkd.in/eHrBJsZH Special thanks to Eben Eliason, Josh Padnick, Tin Nguyen and Zach Goldberg for helping to shape this blog post!

Gruntwork Newsletter, January 2025: The Road to Terragrunt 1.0, Terragrunt Stacks, OpenTofu 1.9 & more https://lnkd.in/gGE_6wEQ

Part 11 of the Fundamentals of DevOps and Software Delivery series is now available! In this post, Gruntwork co-founder Yevgeniy Brikman shares his take on the future of DevOps and Software Delivery: 1?? Infrastructureless: the evolution of serverless. 2?? Generative AI: the impact of LLMs on software delivery. 3?? Secure by default: shift left, supply chain security, memory-safe langs. 4?? Platform engineering: every company wants their own PaaS. 5?? The future of infrastructure as code: infrastructure from code and runbooks. https://lnkd.in/eK5fJkbC

Part 10 of the Fundamentals of DevOps and Software Delivery series is now available! Learn about all about monitoring: 1?? Logging: levels, aggregation, and structured logging 2?? Metrics: collecting, analyzing, and dashboards 3?? Observability: structured events, tracing, testing in production 4?? Alerts: triggers, on-call rotations, and playbooks https://lnkd.in/gC7D5m6z

We just announced The Road to Terragrunt 1.0! Over the coming months, we'll be publishing both blog posts and Terragrunt feature releases that will eventually culminate in Terragrunt 1.0. The major improvements that we announced are: 1. Terragrunt UX and CLI improvements 2. Terragrunt Stacks 3. Terragrunt Remote Runners 4. A stronger Terragrunt community 5. A fancy new Terragrunt logo On a personal note, it was really exciting to finally publish this blog post. There are thousands of Terragrunt users worldwide, and we interviewed dozens of them, plus brainstormed a bunch of ideas internally ourselves. Ultimately, we see a world where every team works with small deployable units of infrastructure, and we'd like Terragrunt to be the best way to accomplish that. We're also excited about the enthusiasm we're seeing with Terragrunt Stacks. For many years now, Terragrunt has done a great job of enabling you to work in small deployable units of infrastructure. With Terragrunt Stacks, we'll be able to help users combine a common set of units to handle use cases like creating new environments, create complex new applications, or standing up new customers. And of course, we're excited to finally have a Terragrunt logo. :) You can read the official blog post at https://lnkd.in/gitE3-us. Feedback welcome as always!