# hashicorp Published articles for hashicorp. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Terraform vs OpenTofu: Which IaC tool fits your platform strategy? DevFeed: [Terraform vs OpenTofu: Which IaC tool fits your platform strategy?]() Original publisher: [Read original article]() Author: Mallory Haigh Published: 2026-07-23T05:40:01Z Content type: article Language: en Sources: [Platform Engineering Blog]() Topics: [Infrastructure as code](), [Terraform](), [Platform Engineering](), [Provisioning](), [Open Source](), [configuration](), [Encryption]() Tags: [governance](), [hashicorp](), [iac](), [infrastructure-as-code](), [multi-cloud](), [open-source](), [opentofu](), [orchestration](), [platform-engineering](), [provisioning](), [strategy](), [terraform]() ### AI overview This guide compares Terraform and OpenTofu as infrastructure-as-code tools. It explains how HashiCorp's 2023 license change led to OpenTofu's creation as a Linux Foundation-governed fork, and frames the choice around platform engineering strategy, governance, licensing, state encryption, and long-term risk. ### Source excerpt HashiCorp's license change sparked the Terraform vs OpenTofu debate. Compare governance, licensing (BSL vs MPL 2.0), state encryption, and strategic fit for your platform engineering strategy. ## Vagrant: entornos de desarrollo reproducibles DevFeed: [Vagrant: entornos de desarrollo reproducibles]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-06T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Vagrant](), [Oracle-VM-VirtualBox](), [Linux]() Tags: [ansible](), [hashicorp](), [rsync](), [ruby](), [snapshots](), [vagrant](), [virtualbox]() ### AI overview A Spanish tutorial explaining how Vagrant defines reproducible development environments as code. It covers installation, provider selection, Vagrantfile configuration, the VM lifecycle, SSH access, and synchronized folders, including performance and consistency considerations for VirtualBox, libvirt, NFS, and rsync. ### Source excerpt Vagrant con libvirt o VirtualBox: carpetas sincronizadas, snapshots, aprovisionamiento con Ansible y reload vs provision. ## Dispelling the myths around incident response with Colette Alexander, Director of Engineering at HashiCorp DevFeed: [Dispelling the myths around incident response with Colette Alexander, Director of Engineering at HashiCorp]() Original publisher: [Read original article]() Published: 2024-04-16T15:11:37Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Incident response](), [incident management](), [Process]() Tags: [engineering](), [hashicorp](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [slack-incident]() ### AI overview This episode of The Debrief examines common myths around incident response with Colette Alexander, HashiCorp's Director of Engineering. The discussion covers learning and process, questioning assumptions after incidents, and why documenting risk does not necessarily help manage it. ### Source excerpt In this episode of The Debrief, we chat with Colette Alexander, Director of Engineering at HashiCorp, about common myths around incident response. ## Making incidents less painful with Kerim Satirli of HashiCorp & Lawrence Jones of incident.io DevFeed: [Making incidents less painful with Kerim Satirli of HashiCorp & Lawrence Jones of incident.io]() Original publisher: [Read original article]() Published: 2024-02-19T02:26:44Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [incident](), [Incident response](), [incident management]() Tags: [hashicorp](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [outage](), [post-mortem](), [slack-incident]() ### AI overview An episode featuring Kerim Satirli of HashiCorp and Lawrence Jones of incident.io discusses ways teams can optimize incident response and make incidents less painful. ### Source excerpt In this episode, we chat with Kerim Satirli of Hashicorp and Lawrence Jones of incident.io on ways teams can optimize their incident response. ## Advice for making incidents less painful with Kerim Satirl of HashiCorp DevFeed: [Advice for making incidents less painful with Kerim Satirl of HashiCorp]() Original publisher: [Read original article]() Author: incident.io Published: 2024-02-16T16:31:08Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Security](), [migration](), [MongoDB](), [ssh](), [servers]() Tags: [database](), [database-migration](), [developer](), [hashicorp](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [mongodb](), [outage](), [post-mortem](), [quick-tips](), [servers](), [slack-incident](), [ssh]() ### AI overview An interview preview with HashiCorp developer advocate Kerim Satirli offers practical advice for making incidents less painful. It discusses recurring security incidents and vulnerabilities, a failed MongoDB data migration, the risks of making changes when teammates are unavailable, and a server lockout caused by a command that prevented SSH access. ### Source excerpt We sat down with Kerim Satirli, Senior Developer Advocate at Hashicorp, to get some quick tips on how teams can make incidents less of a headache. Here's a preview of his responses. ## Update for Chainguard Images users on HashiCorp license changes DevFeed: [Update for Chainguard Images users on HashiCorp license changes]() Original publisher: [Read original article]() Published: 2023-09-01T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [chainguard](), [Security](), [Open Source](), [Terraform]() Tags: [chainguard-images](), [consul](), [hardened-container-image](), [hashicorp](), [open-source](), [opentf](), [releases](), [security](), [terraform](), [vault]() ### AI overview Chainguard explains how HashiCorp's switch from the Mozilla Public License to the Business Source License affects Chainguard Images users. Paying customers receive six additional months of security patches for MPL-licensed HashiCorp tools, while free users retain access to the final MPL-based versions and may receive BUSL-based images through other distribution options. ### Source excerpt Chainguard's proactive approach to HashiCorp license changes: Secure image solution for hassle-free adaptation. ## Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial DevFeed: [Deploying Machines with MaaS and Packer - Metal as a Service + Hashicorp Packer Tutorial]() Original publisher: [Read original article]() Author: Techno Tim Published: 2023-01-28T14:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [Tutorial](), [canonical](), [systems](), [Cloud](), [Linux](), [Windows](), [virtual machines](), [Oracle-VM-VirtualBox]() Tags: [boot](), [canonical](), [cloud](), [dhcp](), [hashicorp](), [how-to](), [linux](), [maas](), [networking](), [operating-systems](), [systems](), [tutorial](), [ubuntu](), [virtual-machines](), [windows]() ### AI overview A tutorial on installing and configuring Canonical MaaS to provision bare-metal and virtual machines, deploy operating systems, configure networking and network boot, commission machines, and create and upload custom images with Hashicorp Packer. ### Source excerpt MaaS or Metal as a service from Canonical is a great way to provision bare metal machines as well as virtual machines.MaaS allows you to deploy Windows, Linux, ESXi, and many other operating systems to your systems helping you to build a bare metal cloud.You can even use Packer from Hashicorp to configure custom images too! We'll cover all of this and more in this tutorial on how to install an... ## A HashiConf art collab DevFeed: [A HashiConf art collab]() Original publisher: [Read original article]() Author: Monica Dinculescu Published: 2021-10-15T00:00:00Z Content type: opinion Language: en Sources: [Monica Dinculescu]() Topics: [color](), [Requirements](), [iteration]() Tags: [art](), [conference](), [custom](), [design](), [generative](), [hashicorp](), [iteration](), [printer](), [printing](), [requirements](), [things]() ### AI overview The article describes creating custom generative-art prints for HashiConf Europe speakers. Each print combines the speaker's name, talk title, and the relevant HashiCorp product color in a randomly generated geometric grid, following conference design guidelines. ### Source excerpt A couple of months ago my friend Jana helped organize HashiConf Europe, and asked me to work on generating custom artwork for each of their speakers. This was my first experience with creating art for someone else, and especially art that had to match someone else's artistic guidelines. I've said this before, but I live and nap by the idea that rules (and editing) are at the core of the artistic process and not having to do that myself was brilliant. I wanted to write a bit about it because a) I did a bunch of work that I'm really proud of and I never got to talk about it and b) I am vain and I want to talk about it. This was the final poster: And this is what we wrote about it on the card that accompanied it: Enclosed you will find an art print made for you by generative artist and engineer Monica Dinculescu. This individual print is unique to you and you alone, as Monica has incorporated your name, the title of your talk, and the color of the HashiCorp product that you are talking about at this year's conference. Each cell in the grid has been randomly generated to contain either a letter from your name, or a pattern in the product color. Cells located towards the middle of the grid are more likely to contain a letter rather than a pattern, and this likelihood decreases in the cells towards the edges. This print is the only iteration of its kind. Were it to be generated again, it would look slightly different each time. I print everything in my art store myself, because I sell very limited editions and third-party printing companies only make sense financially when you're printing in the several dozen. This does mean that sometimes I'll fight with my printer thinking that its colour profile is whack, only to discover that it was Doing Just Fine™ and my MacBook oversaturates things like it's an Instagram filter in 2011. Every day is a school day. Here are all the prints drying on their totes profesh drying rack that is definitely not just a string I hung around in ## Designing a Workflow engine from first principles DevFeed: [Designing a Workflow engine from first principles]() Original publisher: [Read original article]() Author: Shawn Wang Published: 2021-04-05T07:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Architecture & Design](), [Scalability](), [Messaging](), [sharding](), [Routing (disambiguation)](), [consistency](), [Availability](), [Programming](), [Open Source]() Tags: [architecture](), [consistency](), [hashicorp](), [messaging](), [microservices](), [open-source](), [queues](), [routing](), [scalability](), [scalable-architecture](), [temporal](), [temporal-concepts](), [workflow](), [workflow-engine]() ### AI overview This article explains workflow engine design principles from first principles, including task queues, timers, consistency, scalability, sharding, routing, system workflows, and external implementations. It describes how Temporal addresses these requirements and outlines Temporal's history through related systems and projects such as SWF, Durable Task Framework, Cherami, and Cadence. ### Source excerpt Learn key workflow engine design principles and how Temporal's scalable architecture solves challenges like task queues and scalability. ## Target and Elasticsearch: Maintaining an ELK stack over Peak Season DevFeed: [Target and Elasticsearch: Maintaining an ELK stack over Peak Season]() Original publisher: [Read original article]() Author: Target Brands, Inc Published: 2017-05-25T05:00:00Z Content type: article Language: en Sources: [Target]() Topics: [elasticsearch](), [Logging](), [Cloud](), [Monitoring](), [dashboards](), [Scalability](), [Kafka]() Tags: [apache](), [apache-kafka](), [cloud](), [clusters](), [consul](), [contribute](), [dashboards](), [elasticsearch](), [elk](), [hashicorp](), [infrastructure](), [kafka](), [logging](), [logging-and-metrics](), [logs](), [make](), [metrics](), [monitoring](), [open](), [open-source](), [scalability]() ### AI overview This article describes how Target operated and evolved an Elasticsearch-based ELK stack for large-scale log aggregation, search, analytics, and multi-tenant logging during peak production periods. It discusses cloud scalability, operational challenges, and the open-source tools used alongside Elasticsearch. ### Source excerpt One of the strongest benefits of launching an application into the cloud is the pure on-demand scalability that it provides. I've had the privilege of working with the ELK stack (Elasticsearch, Logstash, Kibana) for purposes of log aggregation for the past two years. When we started at that time, we were pleased with our performance on search and query times with 10's of gigabytes of data in the cluster in production. When Peak time hit, we reveled as our production clusters successfully managed half a terabyte of data(!). During peak, Target hosted 14 Elasticsearch clusters in the cloud containing more than 83 billion documents across nearly 100 terabytes in production environments alone. Consumers of these logs are able to get access to queries in blazing fast times with excellent reliability. It wasn't always that way though, and our team learned much about Elasticsearch in the process. What's The Use Case At Target? In a word, "vast." The many teams that use our platform for log aggregation and search are often times looking for a variety of things. Simple Search This one is easy, and the least resource intensive. Simply doing a match query and searching for fields within our data. Metrics / Analytics This one can be harder to accommodate at times, but some teams use our Elasticsearch clusters for near-realtime monitoring and Analytics using Kibana dashboards. Multi-tenant Logging Not necessarily consumer facing, but an interesting use for Elasticsearch is that we can aggregate many teams and applications into one cluster. In essence, this saves money over individual applications paying for infrastructure to log themselves. Simple search is the least of our concerns here. Queries add marginal load on the cluster, but often they are one-offs or otherwise infrequently used. However, the largest challenge faced here is multi-tenant demand. Different teams have very different needs for logging/metrics; designing a robust and reliable 'one-size-fits-all' platform is