Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH

27 views
Skip to first unread message

Geoff Nichols (JIRA)

unread,
Jul 11, 2016, 5:18:02 PM7/11/16
to puppe...@googlegroups.com
Geoff Nichols created an issue
 
Puppet / New Feature PUP-6488
Gem provider should allow alternative gem command; should not rely on $PATH
Issue Type: New Feature New Feature
Assignee: Unassigned
Created: 2016/07/11 2:17 PM
Priority: Normal Normal
Reporter: Geoff Nichols

In PUP-5427, Mikhail T. commented:

  1. 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.
  2. 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...

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Atlassian logo

Ethan Brown (JIRA)

unread,
May 16, 2017, 7:06:03 PM5/16/17
to puppe...@googlegroups.com
Ethan Brown updated an issue
Change By: Ethan Brown
Labels: triaged
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Ethan Brown (JIRA)

unread,
May 16, 2017, 7:06:03 PM5/16/17
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
May 10, 2018, 9:34:02 PM5/10/18
to puppe...@googlegroups.com
Branan Riley updated an issue
Change By: Branan Riley
Labels: gem package triaged type_and_provider
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Branan Riley (JIRA)

unread,
Mar 25, 2019, 5:12:04 AM3/25/19
to puppe...@googlegroups.com

Branan Riley (JIRA)

unread,
Mar 25, 2019, 5:12:04 AM3/25/19
to puppe...@googlegroups.com

Mihai Buzgau (JIRA)

unread,
Apr 3, 2019, 5:58:02 AM4/3/19
to puppe...@googlegroups.com

Sebastian Miclea (JIRA)

unread,
Apr 10, 2019, 5:26:03 AM4/10/19
to puppe...@googlegroups.com

Mihai Buzgau (JIRA)

unread,
Apr 17, 2019, 5:35:10 AM4/17/19
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: PR - 2019-04-17 , PR - 2019-05-02

Mihai Buzgau (JIRA)

unread,
May 2, 2019, 5:21:08 AM5/2/19
to puppe...@googlegroups.com
Mihai Buzgau updated an issue
Change By: Mihai Buzgau
Sprint: PR - 2019-04-17, PR - 2019-05-02 , PR - 2019-05-15

Sebastian Miclea (JIRA)

unread,
May 14, 2019, 8:15:04 AM5/14/19
to puppe...@googlegroups.com
Sebastian Miclea commented on New Feature PUP-6488
 
Re: Gem provider should allow alternative gem command; should not rely on $PATH

Thomas Kishel Could you please add documentation to this ticket so it can be closed?

Thomas Kishel (JIRA)

unread,
May 14, 2019, 1:34:03 PM5/14/19
to puppe...@googlegroups.com
Thomas Kishel updated an issue
 
Change By: Thomas Kishel
Release Notes Summary: 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
Release Notes: New Feature

Thomas Kishel (JIRA)

unread,
May 14, 2019, 1:35:03 PM5/14/19
to puppe...@googlegroups.com
Thomas Kishel commented on New Feature PUP-6488
 
Re: Gem provider should allow alternative gem command; should not rely on $PATH

Release note ready for review.

Thanks for your help with this!

Oana Tanasoiu (JIRA)

unread,
Jun 10, 2019, 3:07:04 AM6/10/19
to puppe...@googlegroups.com

Heston Hoffman (JIRA)

unread,
Jun 12, 2019, 3:51:03 PM6/12/19
to puppe...@googlegroups.com
Heston Hoffman updated an issue
Change By: Heston Hoffman
Labels: gem package resolved-issue-added type_and_provider

Vadym Chepkov (JIRA)

unread,
Jun 19, 2019, 9:24:03 PM6/19/19
to puppe...@googlegroups.com
Vadym Chepkov commented on New Feature PUP-6488
 
Re: Gem provider should allow alternative gem command; should not rely on $PATH

FYI, puppetlabs-puppetserver_gem module is not compatible with this change

Thomas Kishel (JIRA)

unread,
Jun 20, 2019, 2:23:03 PM6/20/19
to puppe...@googlegroups.com
Thomas Kishel commented on New Feature PUP-6488

I've added a commit to the pending PR for the puppetserver_gem module that resolves this:

https://github.com/puppetlabs/puppetlabs-puppetserver_gem/pull/27

The change adds:

  def self.provider_command
    command(:puppetservercmd)
  end

(This is an example of why I suggested the puppetserver_gem provider be moved from a module to Puppet Core.)

Gheorghe Popescu (JIRA)

unread,
Jul 3, 2019, 4:40:03 AM7/3/19
to puppe...@googlegroups.com
Gheorghe Popescu updated an issue
 
Change By: Gheorghe Popescu
Fix Version/s: PUP 6.4.3
Fix Version/s: PUP 6.0.10
Fix Version/s: PUP 5.5.15

Austin Boyd (Jira)

unread,
Jul 25, 2020, 5:32:02 PM7/25/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Labels: gem jira_escalated package resolved-issue-added type_and_provider
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Austin Boyd (Jira)

unread,
Jul 25, 2020, 5:32:04 PM7/25/20
to puppe...@googlegroups.com
Austin Boyd updated an issue
Change By: Austin Boyd
Zendesk Ticket Count: 1 2
Zendesk Ticket IDs: 33048 ,40158

Nick Walker (Jira)

unread,
Sep 10, 2020, 1:22:07 PM9/10/20
to puppe...@googlegroups.com
Nick Walker commented on New Feature PUP-6488
 
Re: Gem provider should allow alternative gem command; should not rely on $PATH

For reference this issue causes the following issue in environments that have puppetserver_gem installed and do not upgrade to v1.1.1.

Could not prefetch package provider 'puppetserver_gem': No command gemcmd defined for provider puppetserver_gem
Failed to apply catalog: No command gemcmd defined for provider puppetserver_gem

Reply all
Reply to author
Forward
0 new messages