Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-1435

Puppet::Util::execute semantics, on Windows, don't match POSIX or Puppet expectations.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Ready for Engineering
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
    • Template:
    • Epic Link:
    • Team:
      Coremunity

      Description

      A whole bunch of code in Puppet expects that you can pass a white-space separated string to `Puppet::Util::execute`, in an array, and have it figure out the executable that should be run.

      For example, in master, [`lib/puppet/resource/type_collection.rb:141`](https://github.com/puppetlabs/puppet/blob/master/lib/puppet/resource/type_collection.rb#L141) has this expectation - and on POSIX platforms, that is satisfied.

      The semantics should probably match on different platforms. This is the last remaining point blocking [external configuration version commands](https://github.com/puppetlabs/puppet/blob/master/spec/integration/parser/compiler_spec.rb#L21) working on Windows, despite what that file says.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              redmine.exporter redmine.exporter
              QA Contact:
              Eric Thompson Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support