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

Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number

    XMLWordPrintable

    Details

    • Epic Name:
      Package resource should allow version constraint
    • Template:
    • Team/s:
      Night's Watch
    • Sprint:
      PR - Triage
    • CS Priority:
      Reviewed
    • Zendesk Ticket IDs:
      38194
    • Zendesk Ticket Count:
      1
    • Release Notes:
      Not Needed

      Description

      It would be helpful if the 'ensure' parameter to the Package resrouce could also specify 'at least version *x' and 'no later than version **y*' as well as 'latest version', 'installed' (IE, any version) or a specific version number.

      EG:

          package { 'foo': ensure=>'>1.0' }

      would act as 'latest' if the current package was uninstalled or version before 1.0, but would act as 'installed' otherwise. Similarly, 

          package { 'foo': ensure=>'<4.0' }

      would act as 'installed' if version is <4.0 but would produce an error otherwise.

      This would allow us to set a manifest to avoid packages with known problems in a certain version, but not upgrade unless necessary.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. PUP-1365 Yum provider doesn't understand globs

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. PUP-5102 Define minimum version for a package

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. PUP-7816 Package resource' ensure attribute to use Semantic Versioning

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. PUP-5541 Package resources should support pessimistic versioning

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. PDB-1872 puppetdb module problems on centos7 after "Add pathing for AIO" commit

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. PUP-6939 New users are confused by package's ensure=>$version

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          [Puppet Labs Redmine] Redmine (#8975) Create comparator parameter to package provider(s)

          [Puppet Labs Redmine] Redmine (#16729) When using the puppetlabs repositories, `yum install puppet` should be safe.

          [Puppet Labs Redmine] Redmine (#16937) Improved Ruby DSL

          [Puppet Labs Redmine] Redmine (#17102) Puppet Package type should support ranges of software versions

          clones

          [Puppet Labs Redmine] Redmine (#12179) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number

            Activity

              People

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

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support