Forge Home

system_gem

Workaround for PUP-6134

18,332 downloads

13,142 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.1.1 (latest)
  • 1.0.7
  • 1.0.6
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2 (deleted)
  • 1.0.1 (deleted)
  • 1.0.0 (deleted)
released Sep 26th 2018
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet > 4.7.0 < 7.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'tkishel-system_gem', '1.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add tkishel-system_gem
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install tkishel-system_gem --version 1.1.1

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

tkishel/system_gem — version 1.1.1 Sep 26th 2018

system_gem

Table of Contents

  1. Description
  2. Usage - Configuration options and additional functionality
  3. Reference - An under-the-hood peek at what the module is doing and how
  4. Limitations

Description

This a workaround for PUP-6134:

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

Usage

Install this module, and specify system_gem as the provider of gem packages.

package { 'sinatra':
  ensure   => present,
  provider => system_gem,
}

Once PUP-6134 has been resolved, specify gem as the provider of gem packages, and uninstall this module.

Reference

On Windows ...

Puppet is unable to manage a ruby gem anywhere other than in Puppet's ruby using the gem package provider. This is caused by Puppet prepending its paths (including the path to Puppet's ruby gem command) to PATH. This workaround removes Puppet's paths from PATH when setting :gemcmd.

Limitations

While the system_gem package provider is meant as a workaround for an issue specific to Windows, it is compatible with the other operating systems supported by the parent gem package provider.