Issue #12179 has been updated by George Herbert.

I would like to add a "metoo" to this feature and describe the situation 
bringing me here.

Current client has a large enterprise and many (say, 100) server types defined. 
 In some cases, we have cases where middleware or tools of a minimum version 
are required for a business application / server type.  In others, we have 
cases where any version up to a limit, but not a later one, is required (app 
does not run with new library, or Tomcat, or whatnot).  In some cases we have 
"works with 1.1 and 1.2 but not 1.0 or 1.3 or later".

We also are having new versions of middleware, tools, and libraries created on 
a regular basis and being qualified for production in a general sense, but not 
necessarily being simultaneously qualified for all of the potentially many 
dozens of app types and versions in use.  So a "latest" becomes highly 
dangerous in these situations.

We can create and curate lists of acceptable versions, or greater than or 
lesser than constraints.  We also can if necessary approve a single "ok" 
version of any given middleware, tool, or library for a given application type 
at any given time, and then rev that across (management domain of set of 
servers, be that all of them enterprise wide or a cluster of them or what).

The flexibility to specify known constraints other than a specific single 
version or a "latest" would be of great help in constructing the business 
process and logic around solving this problem.
----------------------------------------
Feature #12179: Package resource should allow ensure=>">1.0" or ensure=>"<0.10" 
as well as 'latest', 'installed' and specific version number
https://projects.puppetlabs.com/issues/12179#change-83639

Author: Steve Shipway
Status: Needs Decision
Priority: Normal
Assignee: J.D. Welch
Category: language
Target version: 
Affected Puppet version: 2.7.9
Keywords: ux
Branch: 


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. 


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to