Details
-
Epic
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
Package resource should allow version constraint
-
-
Night's Watch
-
ready for triage
-
Reviewed
-
38194
-
1
-
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
-
PUP-1365 Yum provider doesn't understand globs
-
- Closed
-
-
PUP-5102 Define minimum version for a package
-
- Closed
-
-
PUP-7816 Package resource' ensure attribute to use Semantic Versioning
-
- Closed
-
-
PUP-5541 Package resources should support pessimistic versioning
-
- Closed
-
- relates to
-
PDB-1872 puppetdb module problems on centos7 after "Add pathing for AIO" commit
-
- Closed
-
-
PUP-6939 New users are confused by package's ensure=>$version
-
- Closed
-
- clones