garylarizza.com

What is data and what is code?

This issue of what constitutes data is the first wrinkle in devising what I call a data escalation path. For background reading, the Puppet docs page on roles and profiles does a great job of describing the difference between a component module and a profile.

Why an escalation path?

The decisions you make when writing Puppet manifests will seldom be plain and obvious. Instead of focusing on whether something is in the right place, it’s better to think about the ways that complexity can help you solve problems. You can absolutely put everything you would consider data inside Hiera, and that would immediately provide you a way to handle most use cases.

Can/Should we also put other modules inside the Control Repo?

Once you add the site directory to $modulepath, it opens up that directory to be used as a place for storing ANY Puppet modules.

Who owns what?

One of the biggest factors to influence where Puppet modules should be managed is the split of which teams own which decisions.

What the hell is ‘Data’ anyhow?

This point has single-handedly caused more people to come up and argue with me. I’m not kidding. I shit you not, I’ve had people legitimately *SCREAM* at me about how wrong I was with my opinions here.