Issue #6808 has been updated by Daniel Pittman.

Status changed from Accepted to Needs Decision
Assignee set to Nigel Kersten

Nigel, can you classify the severity of this:

A debug message, useful when someone investigates to figure it out?

A notice, which will show up normally, but be strange.

A warning on the client side, but carry on?

An error on the client side (or, correctly, during compilation) if both of 
those are specified?

I lean heavily to the last; in the huge matrix of things you can tell `file` to 
do, this one is invalid, and can be detected, so let us just fail the thing 
honestly and make the user fix it.

Finally, if we do that, where should we target this?  2.6, 2.7, trunk?  It 
would break otherwise "working" manifests, in that they presently do something, 
just not something that the user probably expects...
----------------------------------------
Bug #6808: Provide informative message when ensure => present, *and* managing 
content/source, and target is a symlink
https://projects.puppetlabs.com/issues/6808

Author: Nigel Kersten
Status: Needs Decision
Priority: Low
Assignee: Nigel Kersten
Category: 
Target version: 2.6.x
Affected Puppet version: 
Keywords: 
Branch: 


<pre>
/tmp/foo -> /tmp/bar
</pre>

<pre>
file { "/tmp/foo":
  ensure  => present,
  content => "foo",
}
</pre>

When you run this, you get no indication that the content will not be written. 
This is because the existence of the symlink suffices for "ensure => present", 
and the content isn't evaluated.

This is almost certainly another indicator that we should be breaking the 
symlink type out into it's own type, separate from File, but in the meantime we 
should try to log *something* here if feasible.




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to