Opscode "application" cookbook recipes


#1

Ohai Chefs,

I just merged the pull request for COOK-1820, which removes all the
deprecated recipes from Opscode’s “application” cookbook. The version is
updated to 1.0.5, though the next “Released” version of the cookbook will
be 2.0.0. That is pending some discussion about COOK-1673.

What this means for you:

If you’re using the application cookbook’s recipes (with the data bags for
applications), and you have version 1.0.4, do not update to the latest
master branch. I’d recommend pinning your cookbook version with the
equality operator until such time as you have converted your application
deployment to use the application* cookbooks LWRPs. For example,
environments/production.rb would have:

name "production"
cookbook_versions "application" => "= 1.0.4"

The next release of the cookbook will be version 2.0.0. The "sub resource"
cookbooks (application_ruby, application_php, etc) do not have any
specific changes related to this, so their versions will not have a major
increment.

We’ll send out an announcement to the lists again when the next version
has been released.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#2

Ohai Chefs,

Version 2.0.0 of the application cookbook is released.

This post went to the developers list yesterday. We were waiting for final
touches on COOK-1673, which Andrea Campi provided. Thanks, Andrea!

The following tickets were addressed in this release:

  • [COOK-1673] - Deploy_revision in the application cookbook gives an
    argument error
  • [COOK-1820] - Application cookbook: remove deprecated recipes

Cheers,
Joshua

On 11/20/12 11:45 AM, “Joshua Timberman” joshua@opscode.com wrote:

Ohai Chefs,

I just merged the pull request for COOK-1820, which removes all the
deprecated recipes from Opscode’s “application” cookbook. The version is
updated to 1.0.5, though the next “Released” version of the cookbook will
be 2.0.0. That is pending some discussion about COOK-1673.

What this means for you:

If you’re using the application cookbook’s recipes (with the data bags for
applications), and you have version 1.0.4, do not update to the latest
master branch. I’d recommend pinning your cookbook version with the
equality operator until such time as you have converted your application
deployment to use the application* cookbooks LWRPs. For example,
environments/production.rb would have:

name "production"
cookbook_versions “application” => “= 1.0.4”

The next release of the cookbook will be version 2.0.0. The "sub resource"
cookbooks (application_ruby, application_php, etc) do not have any
specific changes related to this, so their versions will not have a major
increment.

We’ll send out an announcement to the lists again when the next version
has been released.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#3

Thanks for the update. So is COOK-1673 fixed in 1.0.5?

On Tue, Nov 20, 2012 at 10:45 AM, Joshua Timberman joshua@opscode.com wrote:

Ohai Chefs,

I just merged the pull request for COOK-1820, which removes all the
deprecated recipes from Opscode’s “application” cookbook. The version is
updated to 1.0.5, though the next “Released” version of the cookbook will
be 2.0.0. That is pending some discussion about COOK-1673.

What this means for you:

If you’re using the application cookbook’s recipes (with the data bags for
applications), and you have version 1.0.4, do not update to the latest
master branch. I’d recommend pinning your cookbook version with the
equality operator until such time as you have converted your application
deployment to use the application* cookbooks LWRPs. For example,
environments/production.rb would have:

name "production"
cookbook_versions "application" => "= 1.0.4"

The next release of the cookbook will be version 2.0.0. The "sub resource"
cookbooks (application_ruby, application_php, etc) do not have any
specific changes related to this, so their versions will not have a major
increment.

We’ll send out an announcement to the lists again when the next version
has been released.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman


#4

On 11/21/12 10:02 AM, “Leo Dirac (SR)” leo@scaledrecognition.com wrote:

Thanks for the update. So is COOK-1673 fixed in 1.0.5?

Its now merged into master, so “yes” - though we’re going to release 2.0.0
shortly.


Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman