# Cookbook Releases 4/29/2013 Double Scoop

**URL:** <https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889>\
**Category:** Chef Infra (archive)\
**Created:** [April 30, 2013, 2:15am UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889 "2013-04-30T02:15:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joshua\_Timberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshua_timberman/32/424_2.png) [@Joshua\_Timberman](https://discourse.chef.io/u/Joshua_Timberman)\
**Post date:** [April 30, 2013, 2:15am UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/1 "2013-04-30T02:15:04Z")

</div>

Ohai, we meet again!

We have a few more cookbook releases for you. You’ll note that the “changelog” format of these has changed, hopefully for the better! Mike Fiedler provided an excellent little script to grab JIRA data and massage it into something useful. Going forward, we’ll make this output the default in the [CHANGELOG.md](http://CHANGELOG.md) and in these release announcements. Thanks Mike!

If you want to use the script, check it out (most updated is my fork): [https://gist.github.com/jtimberman/5315163](https://gist.github.com/jtimberman/5315163)

(note that the lvm and munin cookbooks were updated before I fixed the issue I had with ‘clformat.rb’, so the [CHANGELOG.md](http://CHANGELOG.md) in those cookbooks doesn’t reflect the formatting, but I put it in the notes below)

## application v2.0.2:

### Bug

- [COOK-2537]: Provide proper `respond_to` behavior when using  
`method_missing`
- [COOK-2713]: application resource should Allow sub-resource  
attributes to propogate up

### Improvement

- [COOK-2597]: Allow customization for shallow\_clone when doing a git  
deploy

## application\_java v1.1.0:

### Bug

- [COOK-2523]: deployments do not follow standards set by the Deploy  
provider

## application\_nginx v1.0.4:

### Bug

- [COOK-2402]: cookbook attribute expects argument to be a string

## application\_php v1.1.0:

### New Feature

- [COOK-2395]: Add an optional “root” parameter
- [COOK-2539]: Add frameworks for deploying

### Bug

- [COOK-2510]: `app_root` is an attribute for php resource instead of  
`mod_php_apache2`
- [COOK-2827]: coerce `cookbook_name` to string

## application\_python v1.2.0:

### Improvement

- [COOK-2611]: Celery LWRP should configure which queues a celeryd  
worker binds to

### Bug

- [COOK-2599]: gunicorn provider fails if no `node['cpu']['total']`

## application\_ruby v1.1.2:

### Bug

- [COOK-2638]: cookbook attribute is not treated as  
a string when specifying `database_yml_template`

### Improvement

- [COOK-2525]: application\_ruby: split runit template into multiple  
lines

## lvm v0.8.8:

### Bug

- [COOK-2283] - lvm version mismatch on fresh amazon linux install
- [COOK-2733] - Fix invalid only\_if command in lvm cookbook
- [COOK-2822] - install, don’t upgrade, lvm2 package

## munin v1.3.0:

### New Feature

- [COOK-2518] - Multi Environment

### Bug

- [COOK-2662] - `munin::server_apache2` fatal due to attribute precendence

---

<div class="post-metadata">

**Author:** ![Cameron\_Johnston1](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/cameron_johnston1/32/548_2.png) [@Cameron\_Johnston1](https://discourse.chef.io/u/Cameron_Johnston1)\
**Post date:** [April 30, 2013, 1:21pm UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/2 "2013-04-30T13:21:41Z")

</div>

Hello Chefs,

I passed a defect in my fix for COOK-2611 which makes application\_python 1.2.0 unusable. A fix has been supplied, so please avoid upgrading until it can be merged.

With apologies,

Cameron

On Monday, April 29, 2013 at 8:15 PM, Joshua Timberman wrote:

> Ohai, we meet again!
> 
> We have a few more cookbook releases for you. You'll note that the "changelog" format of these has changed, hopefully for the better! Mike Fiedler provided an excellent little script to grab JIRA data and massage it into something useful. Going forward, we'll make this output the default in the CHANGELOG.md ([http://CHANGELOG.md](http://CHANGELOG.md)) and in these release announcements. Thanks Mike!
> 
> If you want to use the script, check it out (most updated is my fork): [.jira · GitHub](https://gist.github.com/jtimberman/5315163)
> 
> (note that the lvm and munin cookbooks were updated before I fixed the issue I had with 'clformat.rb', so the CHANGELOG.md ([http://CHANGELOG.md](http://CHANGELOG.md)) in those cookbooks doesn't reflect the formatting, but I put it in the notes below)
> 
> ## application v2.0.2:
> 
> ### Bug
> 
> - [COOK-2537]: Provide proper `respond_to` behavior when using  
> `method_missing`
> - [COOK-2713]: application resource should Allow sub-resource  
> attributes to propogate up
> 
> ### Improvement
> 
> - [COOK-2597]: Allow customization for shallow\_clone when doing a git  
> deploy
> 
> ## application\_java v1.1.0:
> 
> ### Bug
> 
> - [COOK-2523]: deployments do not follow standards set by the Deploy  
> provider
> 
> ## application\_nginx v1.0.4:
> 
> ### Bug
> 
> - [COOK-2402]: cookbook attribute expects argument to be a string
> 
> ## application\_php v1.1.0:
> 
> ### New Feature
> 
> - [COOK-2395]: Add an optional "root" parameter
> - [COOK-2539]: Add frameworks for deploying
> 
> ### Bug
> 
> - [COOK-2510]: `app_root` is an attribute for php resource instead of  
> `mod_php_apache2`
> - [COOK-2827]: coerce `cookbook_name` to string
> 
> ## application\_python v1.2.0:
> 
> ### Improvement
> 
> - [COOK-2611]: Celery LWRP should configure which queues a celeryd  
> worker binds to
> 
> ### Bug
> 
> - [COOK-2599]: gunicorn provider fails if no `node['cpu']['total']`
> 
> ## application\_ruby v1.1.2:
> 
> ### Bug
> 
> - [COOK-2638]: cookbook attribute is not treated as  
> a string when specifying `database_yml_template`
> 
> ### Improvement
> 
> - [COOK-2525]: application\_ruby: split runit template into multiple  
> lines
> 
> ## lvm v0.8.8:
> 
> ### Bug
> 
> - [COOK-2283] - lvm version mismatch on fresh amazon linux install
> - [COOK-2733] - Fix invalid only\_if command in lvm cookbook
> - [COOK-2822] - install, don't upgrade, lvm2 package
> 
> ## munin v1.3.0:
> 
> ### New Feature
> 
> - [COOK-2518] - Multi Environment
> 
> ### Bug
> 
> - [COOK-2662] - `munin::server_apache2` fatal due to attribute precendence

---

<div class="post-metadata">

**Author:** ![Joshua\_Timberman](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/joshua_timberman/32/424_2.png) [@Joshua\_Timberman](https://discourse.chef.io/u/Joshua_Timberman)\
**Post date:** [April 30, 2013, 3:33pm UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/3 "2013-04-30T15:33:59Z")

</div>

Ohai!

On Apr 30, 2013, at 7:21 AM, Cameron Johnston [cameron@rootdown.net](mailto:cameron@rootdown.net) wrote:

> Hello Chefs,
> 
> I passed a defect in my fix for COOK-2611 which makes application\_python 1.2.0 unusable. A fix has been supplied, so please avoid upgrading until it can be merged.
> 
> With apologies

This is merged and released; With hugs! 🙂 -joshua

## v1.2.2:

### Bug

- [COOK-2796]: celery provider tries to case switch on 'queue'  
parameter instead of 'queues' parameter

---

<div class="post-metadata">

**Author:** ![Jesse\_Campbell](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jesse_campbell/32/251_2.png) [@Jesse\_Campbell](https://discourse.chef.io/u/Jesse_Campbell)\
**Post date:** [May 1, 2013, 5:11am UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/4 "2013-05-01T05:11:32Z")

</div>

Hey all, the change for application\_java switches to the standard deploy  
provider from the custom one. Part of that change requires a slightly  
different way of defining the resource.

As a result, it is likely to fail to converge if you just upgrade and  
deploy. Please read up on the new way in the readme to see how it is now  
configured (or feel free to get in touch if things don’t work or are worse  
than before).  
Hopefully this will make things a bit cleaner for anyone who does use the  
recipe!  
-Jesse

---

<div class="post-metadata">

**Author:** ![Mike](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/mike/32/18_2.png) [@Mike](https://discourse.chef.io/u/Mike)\
**Post date:** [May 1, 2013, 1:23pm UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/5 "2013-05-01T13:23:43Z")

</div>

CVP violation?  
If it was a bug, then version should probably be 1.0.1  
If the behavior changed to follow a standard, and broke existing deploys,  
should be a 2.0.0 release.  
Thoughts?  
-M

On Wednesday, May 1, 2013, Jesse Campbell wrote:

> Hey all, the change for application\_java switches to the standard deploy  
> provider from the custom one. Part of that change requires a slightly  
> different way of defining the resource.
> 
> As a result, it is likely to fail to converge if you just upgrade and  
> deploy. Please read up on the new way in the readme to see how it is now  
> configured (or feel free to get in touch if things don't work or are worse  
> than before).  
> Hopefully this will make things a bit cleaner for anyone who does use the  
> recipe!  
> -Jesse

---

<div class="post-metadata">

**Author:** ![Jesse\_Campbell](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/jesse_campbell/32/251_2.png) [@Jesse\_Campbell](https://discourse.chef.io/u/Jesse_Campbell)\
**Post date:** [May 2, 2013, 5:08am UTC](https://discourse.chef.io/t/cookbook-releases-4-29-2013-double-scoop/3889/6 "2013-05-02T05:08:26Z")

</div>

It was originally to have a major version bump... but then we had chef  
conf, so memories faded a bit 🙂

On Wed, May 1, 2013 at 9:23 AM, Mike [miketheman@gmail.com](mailto:miketheman@gmail.com) wrote:

> CVP violation?  
> If it was a bug, then version should probably be 1.0.1  
> If the behavior changed to follow a standard, and broke existing deploys,  
> should be a 2.0.0 release.  
> Thoughts?  
> -M
> 
> On Wednesday, May 1, 2013, Jesse Campbell wrote:
> 
> > Hey all, the change for application\_java switches to the standard deploy  
> > provider from the custom one. Part of that change requires a slightly  
> > different way of defining the resource.
> > 
> > As a result, it is likely to fail to converge if you just upgrade and  
> > deploy. Please read up on the new way in the readme to see how it is now  
> > configured (or feel free to get in touch if things don't work or are worse  
> > than before).  
> > Hopefully this will make things a bit cleaner for anyone who does use the  
> > recipe!  
> > -Jesse