46 feet of hard labor

Imagine climbing 46 feet down that and digging...

I had the amazingly good fortune to spend nearly two weeks in Cuba with an entrepreneurship outreach program recently. As you might imagine, there was a bit of bureaucracy involved. We had to go through several layers of travel agencies and the Cuban government had to approve our detailed itinerary. They're not really known for welcoming this kind of attention on the brilliant Cuban minds working to evolve their economy. It's not exactly clear how well it fits into the Cuban model, you see.

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?

Pages