On 12/09/2013 06:12 PM, Jeff Bachtel wrote:
> When creating a provider that uses a command not in PATH, what is the
> best-practice pattern for case'ing out different potential locations? As
> an example, the puppetlabs rabbitmq pupmod has a rabbitmqplugins
> provider that falls down on CentOS usin
When creating a provider that uses a command not in PATH, what is the
best-practice pattern for case'ing out different potential locations? As an
example, the puppetlabs rabbitmq pupmod has a rabbitmqplugins provider that
falls down on CentOS using the rabbitmq upstream package due to
rabbitmq-plug
