Jira (PUP-2393) evaluate provider after class/resource

[Joshua Cooper (JIRA)]

Title: Message Title

Joshua Cooper commented on an issue   Re: evaluate provider after class/resource The puppet way of doing this currently is to define a feature. Often it is based on the presence of a particular gem being present, but you can confine it based on whatever you want, e.g. https://github.com/puppetlabs/puppet/blob/master/lib/puppet/feature/libuser.rb. And then confine your provider: confine :feature => :yourfeature Puppet will automatically defer evaluation of the resource until its provider becomes suitable. In the specific case of libuser, it controls whether the forcelocal user parameter can be used by the the useradd provider as indicated by: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/user/useradd.rb#L45 Does this approach work for you? Add Comment   Puppet / PUP-2393 evaluate provider after class/resource Providers are currently reevaluated after every package has been installed to ensure the the necessary commands are available. However, providers like pyenv or rvm don't depend on a package, they depend on a vcsrepo or, heaven forbid, an exec which in turn installs the necessary things. There should be a way to tell Puppet to delay evaluating a prov... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.