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 13:05, 2 September 2012
, 2 September 2012→Revertible
| Line 85: | Line 85: | ||
== Revertible == | == Revertible == | ||
Where it's not too difficult, try to write classes so that *removing* a resource will cause a corresponding removal on clients. For example, when ''sudoers::custom { foo: command => "foo" }'' is removed from a client's catalog, the 'foo' command can no longer be run from sudo. To do otherwise could cause nasty security problems! | Where it's not too difficult, try to write classes so that *removing* a resource will cause a corresponding removal on clients. For example, when ''sudoers::custom { foo: command => "foo" }'' is removed from a client's catalog, the 'foo' command can no longer be run from sudo. To do otherwise could cause nasty security problems! | ||
== Syntax == | |||
Puppet gets a little unpredictable around what it does and does not allow in names. To be safe, stick with [a-zA-Z_][a-zA-Z0-9_] for class and variable names, just like C identifiers. In particular, do not use '-' in class or variable names (the latter won't work; the former will almost work). | |||
== Nit-Worthy Code Style == | == Nit-Worthy Code Style == | ||