Managing all the cookbook repos


#1

Hi,

I started adding Berksfile, .travis.yml, activating travis in our
cookbook-org, .kitchen.yml etc. to a couple of repos.

The whole tasks feels a bit cumbersome, so I’m asking how you / opscode
is doing this?

Is this all manual work? I guess not? Yes, berks init. But is there a
way to configure the template that is used to create the Berksfile,
Vagrantfile, etc.?

I’d like to hear a bit about your workflow. Thanks for sharing!

Steffen


#2

CHEF-4062 is along these lines… setting up a configurable template for
’knife cookbook create’… it’d be nice to get a 'knife cookbook fix’
function as well, to edit existing old cookbooks into compliance, but
i’m not sure exactly how that would work…

it would be nice to engineer away some of these yml turds completely and
get them into knife.rb or cookbook metadata.rb

On 12/1/13 4:50 AM, Steffen Gebert wrote:

Hi,

I started adding Berksfile, .travis.yml, activating travis in our
cookbook-org, .kitchen.yml etc. to a couple of repos.

The whole tasks feels a bit cumbersome, so I’m asking how you / opscode
is doing this?

Is this all manual work? I guess not? Yes, berks init. But is there a
way to configure the template that is used to create the Berksfile,
Vagrantfile, etc.?

I’d like to hear a bit about your workflow. Thanks for sharing!

Steffen