Uploaded image for project: 'Puppet Development Kit'
  1. Puppet Development Kit
  2. PDK-406

pdk bundle exec can't find vendored Puppet script

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: PDK 0.6.0
    • Fix Version/s: PDK 1.0.0
    • Component/s: None
    • Labels:
      None
    • Environment:

      Windows 2012 R2
      CentOS 7

    • Template:
    • Epic Link:
    • Team:
      Puppet Developer Experience
    • Method Found:
      Needs Assessment
    • Release Notes:
      Not Needed
    • Release Notes Summary:
      Fixed a bug where `pdk bundle` commands might fail due to not having all vendored Ruby programs on path (in 1.0 release)
    • QA Risk Assessment:
      Needs Assessment

      Description

      The pdk bundle exec command cannot find scripts included with bundled gems, such as puppet.

      Reproduction case

      1. Instal v0.6.0 of the PDK on a Windows 2012 R2 server.

      2. Open a Powershell terminal and create a new module using pdk new module.

      3. Enter the module directory.

      4. Attempt to build the module via pdk bundle exec puppet module build.

      Outcome

      The pdk bundle exec command cannot find a puppet executable:

      PS C:\Users\Administrator\testmod> pdk bundle update
      The dependency puppet-module-posix-default-r2.1 (>= 0) will be unused by any of the platforms Bundler is installing for.
       Bundler is installing for x64-mingw32 but the dependency is only for ruby. To add those platforms to the bundle, run `b
      undle lock --add-platform ruby`.
      The dependency puppet-module-posix-dev-r2.1 (>= 0) will be unused by any of the platforms Bundler is installing for. Bun
      dler is installing for x64-mingw32 but the dependency is only for ruby. To add those platforms to the bundle, run `bundl
      e lock --add-platform ruby`.
      Fetching gem metadata from https://rubygems.org/.........
      Fetching version metadata from https://rubygems.org/..
      Resolving dependencies...
      Using rake 12.0.0
      Using fast_gettext 1.1.0
      Using json 1.8.1
      Using mini_portile2 2.1.0
      Using ffi 1.9.18 (x64-mingw32)
      Using locale 2.1.2
      Using text 1.3.1
      Using public_suffix 2.0.5
      Using spdx-licenses 1.1.0
      Using metaclass 0.0.4
      Using parallel 1.12.0
      Using coderay 1.1.1
      Using method_source 0.8.2
      Using slop 3.6.0
      Using puppet-lint 2.3.0
      Using rspec-support 3.6.0
      Using diff-lcs 1.3
      Using rainbow 2.1.0
      Using jgrep 1.5.0
      Using stomp 1.4.4
      Using systemu 2.6.5
      Using hiera 3.4.0
      Using minitar 0.6.1
      Using ast 2.3.0
      Using powerpack 0.1.1
      Using ruby-progressbar 1.8.1
      Using unicode-display_width 1.3.0
      Using net-ssh 4.1.0
      Using net-telnet 0.1.1
      Using sfl 2.3
      Using bundler 1.15.1
      Using puppet-syntax 2.4.1
      Using nokogiri 1.7.2 (x64-mingw32)
      Using win32-dir 0.4.9
      Using win32-eventlog 0.6.5
      Using win32-process 0.7.5
      Using win32-security 0.2.5
      Using win32-service 0.8.8
      Using facter 2.5.0 (x64-mingw32)
      Using gettext 3.2.3
      Using addressable 2.5.1
      Using mocha 1.1.0
      Using parallel_tests 2.14.2
      Using pry 0.10.4
      Using rspec-core 3.6.0
      Using rspec-expectations 3.6.0
      Using rspec-mocks 3.6.0
      Using mcollective-client 2.11.1
      Using parser 2.4.0.0
      Using net-scp 1.2.1
      Using puppet-module-win-default-r2.1 0.1.0
      Using facterdb 0.3.12
      Using gettext-setup 0.26
      Using json-schema 2.8.0
      Using rspec_junit_formatter 0.3.0
      Using rspec 3.6.0
      Using rubocop 0.49.1
      Using specinfra 2.67.3
      Using puppet 5.0.1 (x64-mingw32)
      Using metadata-json-lint 2.0.2
      Using rspec-puppet 2.6.7
      Using rubocop-rspec 1.15.1
      Using rspec-puppet-facts 1.8.0
      Using puppetlabs_spec_helper 2.3.1
      Using puppet-module-win-dev-r2.1 0.1.0
      Bundle updated!
       
      PS C:\Users\Administrator\testmod> pdk bundle exec puppet module build .
      bundler: command not found: puppet
      Install missing gem executables with `bundle install`
      

      Expected Outcome

      pdk bundle exec should be able to find executables from gems included with the PDK along with any gems added to a Gemfile by a user.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              james.stocks James Stocks
              Reporter:
              chuck Charlie Sharpsteen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support