Issue #13254 has been reported by Jeff Weiss.

----------------------------------------
Bug #13254: default package provider doesn't respect source parameter
https://projects.puppetlabs.com/issues/13254

Author: Jeff Weiss
Status: Unreviewed
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 
Keywords: 
Branch: 


The default package provider on CentOS doesn't use the source parameter.

I have a manifest that contains this:
<code>
<pre>
package { 'graphite-web':
  ensure => installed,
  source => 'file:///root/manifests/source/graphite-web-0.9.9-1.noarch.rpm',
}
</pre>
</code>

It's a system package; I'm telling Puppet where to get it; I expect the 
manifest to work. It doesn't.

As a user (maybe just as a noob), I would expect that since the package is a 
system type of package (i.e. rpm), I shouldn't need to explicitly specify the 
provider.  If I must, then as a user, I must know the implementation details 
that for system packages (implicit/provider-less) Puppet will only try the yum 
provider even though it can't handle the source parameter (or at least a source 
parameter containing a URI).

Here's the logic for how I think it should work:
<pre>
 no provider && no source => system package, use default [yum on CentOS]
 no provider && source => system package,  use (default.supports_source? ? 
default : URI supportable system package command [rpm on CentOS])
</pre>
This works:
<code>
<pre>
package { 'graphite-web':
  ensure => installed,
  provider => 'rpm',
  source => 'file:///root/manifests/source/graphite-web-0.9.9-1.noarch.rpm',
}
</pre>
</code>
But I feel like we needn't explicitly include provider.


-- 
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