This is the second post in a four-part series on why Open Source Puppet users have made the decision to move to Puppet Enterprise. If you’re considering making this change, read on for pros and cons! As more and more businesses are moving from Open Source Puppet (OSP) to Puppet Enterprise (PE), they are experiencing multiple benefits. In this blog series, we’re exploring the biggest benefits we hear from customers about their experience moving from OSP to PE.

Today, it’s difficult to compile a list of all the managed infrastructure you have across your global estate. It’s even more difficult to collect all of the properties and values that make up that infrastructure, such as operating systems, enterprise licenses, networks, disks, mount points, data centers, regions, patch states, hypervisors, and so much more. Nevertheless, it’s ever more critical to have this information at your fingertips.

The Puppet Developer Kit was launched in 2017 to help our users develop high quality modules faster and over the years, it has seen regular development towards that goal. It was designed to be a single install that would provide everything you needed to write, lint, test and publish a Puppet module — and for the most part, that's what it did.

This past June, Puppet launched Puppet Practice Labs — free, hands-on, interactive tutorials you work through right in your browser — no downloads required. We launched with four step-by-step how-tos on using Puppet Enterprise and Bolt. Feedback was overwhelmingly positive. The biggest request we heard? More, please. Good news! We have a whole slew of new Puppet Practice Labs in development. We want to give you a sneak peek, but there’s a catch.

This is the first post in a four-part series on why Open Source Puppet users have made the decision to move to Puppet Enterprise. If you’re considering making this change, read on for pros and cons! As more and more businesses are moving from Open Source Puppet (OSP) to Puppet Enterprise (PE), they are experiencing multiple benefits. In this blog series, we’re exploring the biggest benefits we hear from customers about their experience moving from OSP to PE.

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.

In my time as a systems engineer in the insurance industry, I learned a lot about compliance programs and the challenges that organizations face to ensure infrastructure is compliant. Audits were time-consuming and handoffs between security, compliance, and infrastructure operations teams were always challenging.