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

Puppet resource should always emit the provider

    XMLWordPrintable

    Details

    • Template:
    • Team:
      Coremunity
    • Sprint:
      Platform Core KANBAN
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      The "puppet resource <type>" command returns resources from all suitable providers. Previously, the name of the provider was not included in the output. However, the result was ambiguous for resource types like "package", which support multiple providers at the same time, e.g. "yum" and "gem". The "puppet resource" command now returns the name of the provider so that resources are uniquely identified.
      Show
      The "puppet resource <type>" command returns resources from all suitable providers. Previously, the name of the provider was not included in the output. However, the result was ambiguous for resource types like "package", which support multiple providers at the same time, e.g. "yum" and "gem". The "puppet resource" command now returns the name of the provider so that resources are uniquely identified.

      Description

      puppet resource <type> [<name>] should always return the provider in the list of discovered resources, as it's possible for the same package name to exist in multiple package providers, e.g. guid.

      PUP-1073 added the ability to specify multiple packages with the same name but different providers. However, 'puppet resource package <name>' only returns one matching package, even if multiple with that name are present. If a package from the default provider and a secondary provider are installed, there seems to be no way to confirm with puppet that the package from the secondary provider is installed.

      We should add a way to do that, probably by enhancing 'puppet resource package <name>' to return multiple results.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              josh Josh Cooper
              Reporter:
              michael.smith Michael Smith
              QA Contact:
              Eric Thompson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support