diff options
| author | Jon Cowie <jcowie@etsy.com> | 2015-02-13 12:12:13 +0000 |
|---|---|---|
| committer | Jon Cowie <jcowie@etsy.com> | 2015-02-13 12:12:13 +0000 |
| commit | 3386dff3694a229993eb11c21baa493fa09a025f (patch) | |
| tree | eb2cbae4cbe229b8b3dbe7bff1172f2891629cfa /DOC_CHANGES.md | |
| parent | 49156a559ecdd88c2d7d183c7ace4d77d185a384 (diff) | |
| download | chef-3386dff3694a229993eb11c21baa493fa09a025f.tar.gz | |
Updated version of #2125 to fix CHEF-2911
This pull request allows a version requirement such as ` = 1.0.1` to be specified in either the resource name or the version attribute of a yum_package resource, and modifies the yum package provider to update existing packages based on that requirement. Also adds specs to test this new functionality.
Diffstat (limited to 'DOC_CHANGES.md')
| -rw-r--r-- | DOC_CHANGES.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md index e1b90d304d..e85e546ee9 100644 --- a/DOC_CHANGES.md +++ b/DOC_CHANGES.md @@ -52,3 +52,9 @@ will stop chef_gem from automatically installing at compile_time. False is the recommended setting as long as the gem is only used in provider code (a best practice) and not used directly in recipe code. +## Yum Package provider now supports version requirements + +A documented feature of the yum_package provider was the ability to specify a version requirement such as ` = 1.0.1.el5` in the resource name. +However, this did not actually work. It has now been fixed, and additionally version requirements are now supported in the `version` attribute +of yum_package as well. + |