2019

unicode date format patterns are a little more nuanced than the “standard” strftime() supported formats. note the difference between the following: man strftime (linux) %y The year as a decimal number without a century (range 00 to 99). (Calculated from tm_year) %Y The year as a decimal number including the century. (Calculated from tm_year) man strftime (osx) %Y is replaced by the year with century as a decimal number. %y is replaced by the year without century as a decimal number (00-99)....

i’m curious as to how long this link will last. that said, pretty solid advice and reasonable take on things. far less abrasive than his twitter feed would have you think.

tl;dr - make a list of all of the annoying places where you need to hardcode DNS entries. you’ll thank yourself later. i retired a DNS server this past week. couple that with the expiration of a couple of guest wifi passes and i discovered that there’s a hidden DNS setting on the APs that can make captive portal DNS resolution miserable if the DNS server is offline. on ubiquit APs the preferred DNS server in the AP is what’s used for the resolution of DNS for the hotspots....

the following will take the output from a json object and flatten it into a key-value path. this is particularly handy when you’re looking to parse out the supported paths in a given device. note: you need to remove the \s from this output and put the entire jq string on the same line. jq '[leaf_paths as $path \ | {"key": $path | join("/"), "value": getpath($path)}] \ | from_entries' foo.json alias to make life happy....

for those times when you just want to run the playbook against a single host in the group … --limit hostname make sure that the host can be found in the inventory.