Here is the puppet script with all the available puppet log functions. log_levels.pp node default { notice(“try to run this script with -v and -d to see difference between log levels”) notice(“function documentation is available here: http://docs.puppetlabs.com/references/latest/function.html”) notice(“————————————————————————–“) debug(“this is debug. visible only with -d or –debug”) info(“this is info. visible only with -v or … Read more
Since Puppet 2.6.0 a new feature “relationship syntax” was introduced. An example in Puppet 2.6.0 and above would look like this: exec { “apt-update”: command => “/usr/bin/apt-get update” } Exec[“apt-update”] -> Package <| |> Every time a package command is executed, the dependency (in our case ‘apt-update’) will be triggered fist. You can even define … Read more
The .dockerignore file is similar to the .gitignore syntax. Here are some example rules: # Ignore a file or directory in the context root named “modules” modules # Ignore any files or directories within the subdirectory named “modules” # in the context root modules/* # Ignore any files or directories in the context root beginning … Read more
They are very different things, actually. To say require B means B must come before A (and, therefore, can lead to circular dependencies if something in B turns out to require A). And if B is not included at all, it will lead to missing dependencies error. On the other hand, include B just says … Read more
Have you tried this? onlyif => “test ! -f /usr/local/bin/papply” Not sure if Puppet can use the ‘!’ character Perhaps a better alternaltive: creates => ‘/usr/local/bin/papply’ even if i don’t like the fact that the command doesn’t really creates the file
The commands in an Exec resource either have to be fully qualified (i. e. /usr/bin/test instead of test) or the path attribute of that Exec resource has to be set. If you can modify the Puppet manifest(s) you can simply add the following definition for setting a default path attribute for all Exec resources to … Read more
Now I suffer from a mental buffer overflow and little confidence of ever being able to tame this beast. First: Relax. I’ve learned that, when you’re new to something with a learning curve such as Puppet, it is pretty easy to become overwhelmed and not be able to get much done. is his login thebob … Read more
Inside templates you have access to a scope object. All of the functions that you can access in the puppet manifests can be accessed via that scope object, although not via the same name. Prepend “function_” to the beginning of the function name. For example, here I included one template inside another: <%= scope.function_template(“template2.erb”) %> … Read more
Yum supports plugins, so it’s entirely possible to write a plugin that reads the cached puppet manifest and warns when a transaction will overwrite a puppet-controlled file. I’m not aware of an existing plugin that does this, but I will probably write just wrote one myself as I like the idea. The plugin checks all … Read more
Take a look at my “renaming” definition for ideas. It assumes Debian, and might work on Ubuntu as well. define rename() { # We only need puppet so we can restart it. In practice, there’s # little point in renaming a machine through puppet without a # running puppet service include puppet::conf # We only … Read more