canmove, Confirmed users
1,394
edits
ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/PuppetAgain/HowTo/Hack on PuppetAgain (view source)
Revision as of 19:00, 4 June 2013
, 4 June 2013→Nit-Worthy Code Style
| Line 110: | Line 110: | ||
* Manifests that are not very obvious by their name should have a very brief comment at the top of the file describing it, these comments are informative, normative reference is the wiki docs. | * Manifests that are not very obvious by their name should have a very brief comment at the top of the file describing it, these comments are informative, normative reference is the wiki docs. | ||
* When it helps understanding of why something is in the manifest (or not in the manifest) please include brief comment saying so. | * When it helps understanding of why something is in the manifest (or not in the manifest) please include brief comment saying so. | ||
== Tips == | |||
In a template, if you have a variable that may be a single value or an array, and you need it to be an array, use | |||
Array(@var) | |||
to convert it to an array. If the array may be created from other arrays in the puppet DSL (which does not support concatenation of arrays), use | |||
Array(@var).flatten | |||
= Landing Changes = | = Landing Changes = | ||