There's no way to do DNS lookups in a template with stock Puppet, but you can
pretty easily write a custom function to do that for you. By default, Resolv
will use the settings in /etc/resolv.conf, so as long as your nameservers are
set up correctly on the puppetmaster, you shouldn't run into an
You still can't use anything other than a string as a resource title. Since
you're passing an array of hashes, it's being converted to a string,
specifically by Puppet::Resource::Type#set_name_and_namespace, which does
@name = name.to_s.downcase.
In your case, you'll probably want to use the cr
Puppet is not really designed to do what you're asking. The idiomatic
Puppet way to install ksh on all your nodes would be to create a node
declaration for each host and either add Package[ksh] on each node or have
them include a class with that resource definition.
If you're looking for a way
Like I said, these aren't "issues" with Puppet, you're just using a
screwdriver to hit a nail. All resources only apply to the local machine.
Your manifests are supposed to declaratively describe what the state and
configuration of a node should be, and the Puppet agent makes it so after
compil
cron::daily is actually a defined resource type, so you need to declare
that resource as opposed to including a class. If you have multiple nodes
that you would like to include the same cron job on, you can write your own
class that declares a cron resources and include that.
It's hard to say w
te:
>
> On Monday, October 29, 2012 4:19:11 PM UTC-7, Jenner La Fave wrote:
>>
>> cron::daily is actually a defined resource type, so you need to declare
>> that resource as opposed to including a class. If you have multiple nodes
>> that you would like to include the
