Issue #5588 has been updated by Nigel Kersten. Status changed from Needs Decision to Closed
The issue in #5525 is actually due to bad conversion between a comma-separated string and an array within a specific provider... and a more generic solution is problematic. Types that do this sort of conversion should do it properly, but as a general solution we should discourage it. ---------------------------------------- Bug #5588: resources should be agnostic about options=>["a","b"] versus options=>"a,b" https://projects.puppetlabs.com/issues/5588 Author: Alan Barrett Status: Closed Priority: Normal Assignee: Nigel Kersten Category: language Target version: Affected Puppet version: Keywords: Branch: Some resources take parameters that puppet expects to be specified as lists, but users expect to be strings with embedded commas. For example, <pre> # wrong ssh_authorized_key { "foo": options => "command=\"...\",no-pty" } # right ssh_authorized_key { "foo": options => ["command=\"...\"", "no-pty"] } # wrong cron { "bar": command => "...", minute => "0,30" } # right cron { "bar": command => "...", minute => [0,30] } </pre> It would be nice if puppet internally split the relevant strings into lists, so that the user does not get confusing errors. -- 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.
