The internet is full of data… and full of data about data (metadata). It is presented to us in many ways. There are tables and lists and graphs (Oh My!), all just a mouse-click away (or maybe two, or seven, or maybe you need pages to get through it). However, there are many reasons you may want your data in a different format. Perhaps you need a new way to gather/present data for accessibility reasons, or perhaps you simply need to be able to save it offline. Maybe you want to send a memo to your boss (or professor) showing how many people have cloned your GitHub repo (or, in the case of my demo, we’ll demonstrate how many people have starred it). Maybe your organization requires a listing of trouble tickets that requires some field manipulation that the GUI itself cannot perform. Or maybe you want to leave your job as a software developer and become a social media specialist, so you’d like to quantify your twitter popularity in a spreadsheet… So, let’s learn about APIs!
In the course of developing and testing various components for working with
Puppet, I had a particularly difficult time with stubbing calls to other Ruby
objects outside of my control.
After a ridiculous amount of searching, I finally found the answer that made
the whole process seamless.
While creating a custom type for cleaning up
on the system, I needed to get a list of services that were running on the
This is also something that the
svckill native type requires, and was
implemented manually in the past, so I thought that there had to be a more
reusable method built into Puppet.
I recently was attempting, with little success, to set a custom environment for a subset of rspec-puppet tests. After much Googling and perusing the rspec-puppet code base, I finally came up with a method that met my needs nicely.
The second in hopefully many module releases from Onyx Point, an Rsync native type has been posted to Github.
You can get the code at https://github.com/onyxpoint/pupmod-rsync.