cannot be understood is not a virtue. It is a very bad
thing.
On Wednesday, April 24, 2013 6:19:13 AM UTC-7, jcbollinger wrote:
>
>
>
> On Tuesday, April 23, 2013 4:52:11 PM UTC-5, Mike Power wrote:
>>
>> I have been backed into a corner, by they way puppet works,
The difference between 'a' and 'b::b' was that 'a' didn't have a file
declaration, it had a resource declaration that had a file declaration. So
if I created a new resource that wrapped 'b::b' then I got a straight
forward parse-order dependency.
I tend to use defined because it allows you t
I have been backed into a corner, by they way puppet works, but some third
party module.
Basically I have two resources defined:
a {$somevar:}
b::b {$somrvar:}
both have code that looks something like this:
if (!defined(File[$name])) {
file { $name:
...
}
According to the docum
Have anyone of you every seen puppet invert a dependency?
Say I have a class like so:
class jenkins {
user {"jenkins":
ensure => present,
}
}
That should form a dependency like so User[jenkins] => Class[jenkins].
That dependency means that the user jenkins will b
I'll see if I can open source the component I wrote and upload it to puppet
forge. In this way the open source community can continue the debate about
what is the best way to do this, while at the same time those who want can
use some solution other than mkdir -p
--
You received this message
Actually I found if I created a resource between path and file called
element, I could give it a unique name. Then inside the body I could check
to see if the File is declared, if not I could declare it.
On Thursday, April 4, 2013 9:23:54 AM UTC-7, Mike Power wrote:
>
> Puppet rig
Puppet right now requires every element of a path to have an individual
file definition. This makes it had to take an arbitrary path as a
parameter. You are forced to require your client to make the entire path
structure for you or instead you use an exec resource and call mkdir -p.
Using an
your nodes need to
> download modules?
>
> On Friday, March 15, 2013 9:24:36 AM UTC-7, Mike Power wrote:
>>
>> I want to setup a node using a three step process
>> 1) download node requirements (git)
>> 2) download modules to fit requirements (puppet)
>> 3) Brin
n
structure underneath that folder. I am not sure what the folder is and I
am even less sure that I could produce it in house.
Have people solved this problem? What has been their approach?
Mike Power
--
You received this message because you are subscribed to the Google Groups
"Puppet Us
I want to setup a node using a three step process
1) download node requirements (git)
2) download modules to fit requirements (puppet)
3) Bring up the node in the required state (puppet)
The second step is the one I am having trouble with. I want a file
(master.pp) to list out all the modules an
10 matches
Mail list logo
