[chef] Re: Re: Install specific chef version using omnibus

[Tim Smith < >]

Bryan,

Has Opscode put together a policy on retention of previous versions of
Chef within the Omnibus installer?  I am a bit hesitant to use a script to
install a very critical part of my infrastructure without certainty that
the version I need will be there in the future.  Older versions of Chef 10
are already missing from apt.opscode.com, but the use of debs allows
anyone to archive off versions they rely on to a local repository.  That
goes away if you rely on a script to install Chef.  While I'd like to
always run the current release of Chef, parts of my infrastructure still
run on Chef .9 and upgrading it tricky sometimes.  Will there be a posted
lifecycle for each release?

Thanks,
Tim




On 9/12/12 8:57 AM, "Bryan McLellan" 
<
 >
 wrote:

>On Wed, Sep 12, 2012 at 11:34 AM, Jon-Erik Schneiderhan
><
 >
> wrote:
>> curl -L http://www.opscode.com/chef/install.sh ;| sudo bash
>
>sudo true && curl -L https://www.opscode.com/chef/install.sh ;| sudo
>bash -s -- -v 10.12.0
>
>The sudo true is to ensure you get asked the password immediately if
>needed, otherwise the password prompt can be confusing.
>
>-s explicitly tells bash to take input from stdin
>-- tells bash to stop interpreting arguments for itself
>-v 10.12.0 as Dan mentions, tells install.sh what Chef version to
>download.
>
>Unfortunately the API that serves these files doesn't know about
>versions of Chef before 10.12.0. You can find older Omnibus packages
>in the old archive here:
>
>https://opscode-full-stack.s3.amazonaws.com/
>
>What bug are you seeing? Are you using 10.14.0 or 10.14.2?
>
>Bryan