[PUP-6488] Gem provider should allow alternative gem command; should not rely on $PATH - Puppet Jira Server

XML

Word

Printable

Details

Type: New Feature
Status: Resolved
Priority: Normal
Resolution: Fixed
Affects Version/s: None
Fix Version/s: PUP 5.5.16, PUP 6.0.10, PUP 6.4.3, PUP 6.5.0
Component/s: None
Labels:

Team:
Night's Watch
Sprint:
PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15

Zendesk Ticket IDs:
33048,40158
Zendesk Ticket Count:
2

Release Notes:
New Feature
Release Notes Summary:

Hide
Package providers now support a targeted package management command

Puppet package providers use `which` to find the first package management command (for example: `gem` for Ruby, `pip` for Python) in the `PATH`. That prevented Puppet from managing other installations of the same software.

This release adds a `targetable` feature to the Package type, allowing Package providers to implement a `command` attribute. The gem and pip providers now implement that attribute.

```
package { 'colorize':
  name => 'colorize',
  provider => gem,
}

package { 'colorize-opt':
  name => 'colorize',
  provider => gem,
  command => '/opt/ruby/bin/gem',
}
```

This feature allows Puppet to manages the packages in software collections (multiple versions of the same software) such as Red Hat Software Collections.

~~PUP-1082~~, ~~PUP-6488~~

Show
Package providers now support a targeted package management command Puppet package providers use `which` to find the first package management command (for example: `gem` for Ruby, `pip` for Python) in the `PATH`. That prevented Puppet from managing other installations of the same software. This release adds a `targetable` feature to the Package type, allowing Package providers to implement a `command` attribute. The gem and pip providers now implement that attribute. ``` package { 'colorize':   name => 'colorize',   provider => gem, } package { 'colorize-opt':   name => 'colorize',   provider => gem,   command => '/opt/ruby/bin/gem', } ``` This feature allows Puppet to manages the packages in software collections (multiple versions of the same software) such as Red Hat Software Collections. PUP-1082 , PUP-6488

Description

In ~~PUP-5427~~, mi commented:

The gem-provider should not rely on the $PATH for the default gem – it must explicitly invoke the gem-executable appropriate for the underlying OS. On Linux that's /usr/bin/gem, on FreeBSD that's typically /usr/local/bin/gem and so on.
The gem-provider must allow specifying an alternative gemcmd. People have been asking for this for years. Something like:
  package {'foo':
    ensure   => 'latest',
    provider => 'gem',
    gemcmd   => '/usr/local/bin/gem22'
  }
ought to work. But does not...

Attachments

Issue Links

is duplicated by

PUP-10604 Include the puppetserver_gem package provider with core Puppet

Resolved

relates to

PUP-5427 incorrect path being defined in puppet-agent's init script is causing gems to be installed into puppet's gem env.

Resolved

PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows

Resolved

PUP-2730 source attribute not honored for gem provider

Closed

PUP-3688 Allow path environment to be specified on a per-resource basis

Closed

PUP-1082 pip provider should handle multiple pips/pythons

Resolved

links to

"Allow alternate 'gem' command in gem provider"

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...

(1 relates to, 1 links to, 7 mentioned in)

Activity

People

Assignee:: Sebastian Miclea

Reporter:: Geoff Nichols

Votes:: 1 Vote for this issue

Watchers:: 7 Start watching this issue

Dates

Created:: 2016/07/11 2:17 PM

Updated:: 2020/09/10 10:21 AM

Resolved:: 2019/05/15 2:05 AM