Friends don't let friends commit puppet code with obvious errors. Especially when you're working with a team, having a consistent style enforced by something like puppet-lint means less messy diffs as you send changes to each other to review.
Socially, Slack and Twitter are the two poles I gravitate between: Slack for when I'm hoping to be a burden on or distracted by our always-up-to-something community, and Twitter when I'm more in the mood to consume the echo chamber than reverberate sound out in to it.
If you are familiar with Jamf Pro's (formerly the JSS/Casper Suite's) model of smart groups and extension attributes (or EA's), they provide a way to run code that can (among other things) inventory the state of a computer.
For the next stop in our journey, we'll review that jolly ol' soul, Santa. It's a system for either monitoring what apps are launched and blacklisting the ones you decide are bad, or locking down a macOS computer to only run the ones you've whitelisted.
There are two reputations(at least) that your faithful writer is hoping to shake: #1, I do not work for Google. #2, I am not the 'osquery guy'. I don't even know any C++! (I'm going to make time for this eventually, though.
Let's say your company is a place where no one works day-to-day logged in as an admin on their Mac.
You've read the Mule, you've read Ars, and folks like Mactracker have gone out and moved their feed to https like good citizens. But what about those old, abandoned apps we still want to keep using? Well, this is why it's called risk management and not fire-proofing.
As if you haven't heard, there's something new this month to cause drama on the Apple upgrade treadmill (just as nefarious as Slack dragging everyone's communication watering hole into the future). This time it's the coming System Integrity Protection and other tightening restrictions we're all dealing with.
As part of a security initiative to make distinct firmware passwords per machine and escrow them to Crypt's newly distinct 'secrets' database table, I came up with the idea to make an analogue to the Password Assistant you see in Keychain Access or the Accounts pane of System Preferences.
Picking up where we left off with Jenkins, let's look at one possible workflow to get autopkg projects working. Specifically when paired with Munki, this requires a bit more thought, but the Jenkins 'workspace' model and sane use of variables allows us to make one all-purpose script for most contingencies we'd deal with.
