HashiCorp Terraform is an open source Infrastructure as Code (IaC) tool that is widely used to deploy cloud infrastructure in the public cloud, such as AWS and Azure, along with on-premises VMware vSphere environments. One of the challenges is developing a method for bootstrapping the instances with configuration management agents such as the Puppet Enterprise agent.

This blog is the fourth in a four-part series on infrastructure automation for government agencies that are modernizing digital systems while grappling with budget and staffing constraints and the challenges of COVID-19. Read the third post here. For government agencies, continuous modernization is quickly becoming the norm. And, in light of COVID-19, modernizing in cloud environments is now a mission-critical imperative.

Throughout my career within the compliance and security space, I’ve seen the practice of proactively managing digital risk move from a nice-to-have to a must-have for enterprise organizations. And over the last 5 years, things have shifted drastically. Personally, it reminds me of the classic “Dry Bones” nursery rhyme song that my son loves so much which points out how all the different bones are connected to make one body.

Do you author plans for Puppet Enterprise? Looking for ways to improve them? Read on! The Puppet Plan language allows a variety of methods to pick targets. In this article we will explore two of these methods (TargetSpec parameters and PuppetDB queries) and how plan authors can employ the latter to: Note: the following examples assume that you are running against targets that have the Puppet agent installed.