This note is motivated by a conversation between myself, Volcane, and windowsrefund on IRC this afternoon. Volcane would expect the append operator to modify the original array in the global scope and not "copy" the array into the current scope, modifying the copy. Signed-off-by: Jeff McCune <email@example.com>
This tutorial uses known-working examples I have tested and verified with Puppet version 2.6.0. I placed the section immediately after the class parameters section since run-stages requires a functional understanding of parameterized classes in order to specify the stage. Signed-off-by: Jeff McCune <firstname.lastname@example.org>
There were numerous syntax errors which would parse correctly in puppet 2.6.0. There were numerous references to foo and bar metasyntactic variables, which are not easily understood. These references have been replaced with concrete references to the ntp package, file and service. Added natural language translations of the puppet language examples to aid understanding. Signed-off-by: Jeff McCune <email@example.com>
I split the link up on a different line from the link text. Turns out markdown doesn't like that. Also a small sentence structure fix.
There are examples for pretty much everything that can be accessed via the rest API. There's still plenty todo to make this better, but we should get something up for now. I'll be getting this reviewed by another developer tomorrow as long as no urgent bugs get in the way. Finish documenting the security file settings List the supported formats for each API call. Currently this is difficult and many formats that are supposedly supported return bad data like the stringification of a class. Figure out why report only allows PUTS not GETS, and PUTS fail with a (0 of 1) argument error. The Key at the end of the URI should be optional if it's not necessary.