For example I have php-fpm installed:
Name : php-fpm Arch : x86_64 Version : 5.4.16 Release : 23.el7_0.3 Size : 4.5 M Repo : installed From repo : updates Summary : PHP FastCGI Process Manager URL : http://www.php.net/ License : PHP and Zend and BSD
The goal is to keep PHP on the latest 5.4 release. Currently I have this in the manifest:
ensure => '5.4.16-23.el7_0.3',.
That won't update if a new version or release comes out, while I don't want it to update to 5.5 unexpectedly.
I have tried the following:
ensure => '5.4.16',
ensure => '5.4',
ensure => '5.4.16-*',
ensure => '5.4.*',
All of which give me something similar to:
change from 5.4.16-23.el7_0.3 to 5.4 failed: Could not update: Failed to update to version 5.4, got version 5.4.16-23.el7_0.3 instead
This being on RHEL/CentOS it is probably meet the requirement to simply have
ensure => latest, for PHP, I am just using PHP as an example. I stil like to know:
- The puppet way to manage minor releases. (If there is one, or two... I read that at least you can maintain your own repo, but is there a pure puppet syntax like the one I guessed above?)
- There are obviously packages other than PHP, how would you use puppet to manage packages from that are perhaps from different repo, or perhaps for a distro other than RHEL/CentOS, etc.
- I read from the puppet reference that the ensure "values can match /./", is that regex or what? http://docs.puppetlabs.com/references/3.7.5/type.html#package-attribute-ensure
I am running open source Puppet 3.7.5 on RHEL/CentOS 7.