On 12/03/2010 09:48 PM, Don Jackson wrote:
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured machine via a recursive file
resource.
What I would like
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured machine via a recursive file resource.
What I would like to do is create a symlink from the parent
Why not sync the files directly to that directory?
On Dec 3, 2010, at 12:48 PM, Don Jackson wrote:
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured
On Dec 3, 2010, at 12:56 PM, Patrick wrote:
Why not sync the files directly to that directory?
There are other files in the parent directory that are not managed by puppet.
And the names of the files are dynamic enough that it would be painful to
explicity manage each file in the puppet
The catalog that is shipped to the client is immediately applied
without reevaluating the state of the client (that evaluation is done
during catalog compilation on the master with the provided facts).
I think what you're looking for is for puppet to download a catalog,
revise the resources that
Puppet won't bother other files in a directory it manages unless you turn on
purge = true.
On Fri, Dec 3, 2010 at 2:15 PM, Don Jackson
puppet-us...@clark-communications.com wrote:
On Dec 3, 2010, at 12:56 PM, Patrick wrote:
Why not sync the files directly to that directory?
There are
On Fri, Dec 3, 2010 at 12:48 PM, Don Jackson
puppet-us...@clark-communications.com wrote:
So here is a scenario:
I have a directory:
./foo
./foo/file1
./foo/file2
./foo/file3
…
./foo/fileN
I populate this directory on a configured machine
