puppet

Environments no longer leak!

Some time ago, I wrote about Environment Leakage, and I'm happy to report that this is much less of a problem today. As of Puppet 4.8 and Puppet Enterprise 2016.5, most custom types will no longer be subject to environment leakage. It's transparent for the end user, when Puppet Enterprise Code Manager is configured, and can be used in Puppet Open Source by following the documentation.

Puppetlinter dot com

A while back I created the http://puppetlinter.com website. It allows you to quickly and easily validate Puppet code against several different versions of Puppet. Today Josh had an idea. Why not a bookmarklet to easily validate Puppet code from a website. Why not?

Validate Puppet Code

  1. drag the bookmarklet link above to your bookmarks menu.
  2. Highlight some code on a webpage.
  3. Click your bookmarklet link.

In other news, spaceships have side effects.

Managing resource dependencies with Puppet is relatively straightforward. You describe any relationships with metaparameters and Puppet figures out the order it should enforce them in. Most dependency issues arise when users try to overspecify dependencies as if they were writing a shell script. Puppet works best when you think in terms of relationships and dependencies rather than ordering.

But there is one giant sticky issue. What about when you don't know the exact resources you need to set relationships on ahead of time?

Docker Docker Docker

Docker docker docker

One thing we do a lot of at Puppet Labs is release product. And every time we make a major product release, I have to go through and update our training material. I validate all the exercises and examples and code snippets. And when we make UI refreshes I have to take all new screenshots. That doesn't sound like much--it's just taking some pictures, right? Well, yeah... but what am I going to take pictures of? Just firing up a master and screenshotting away isn't very interesting or informing.

Pages