Ok, you certainly have a working counter example, but I feel that it
*should* actually fail and that this is a bug.
The expected state of the system is:
1) Make a FIFO file at /other/path
2) Set permissions on /other/path
3) Link /path/link to /other/path
I would like to propose that symlinks sh
Priorities
-
Puppet Agent 1.0.0
-
Puppet Server 2.0.0
-
Puppet Server 1.1.0
-
Puppet 4.0.0 / 3.8.0
-
Hiera 2.0
Our main emphasis continues to be on the work needed to release
puppet-agent 1.0.0 and puppet-server 2.0.0. Much of this is Jenkins-related
(feel free
On Thursday, February 26, 2015 at 2:28:22 PM UTC-6, David Schmitt wrote:
>
> On 2015-02-26 20:31, John Bollinger wrote:
>
> > Symbolic links do _not_ have the same kind of relationship with their
> > targets. A link can be managed entirely independently of its target,
> > therefore Puppet s
I still can't come up with a scenario where this would ever be an issue.
Auto-creating a resource (especially a directory) is a greater level of
spooky action at a distance since it's actually *doing* something to your
system and I'm very against that when possible. (It also bloats your
catalog, b
Hi,
thanks for building this.
I must admit, I find the prospect a little frightening. The logic that
picks the autorequire target makes sense, but I see quite some potential
for surprising the user with weird dependency cycles.
What I'd like to see instead would be for the user type to actually
