[chef] Re: Re: Re: Re: Chef in "Pure Infrastructure-As-Code" Mode?

Chronological Thread 
  • From: Torben Knerr < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Chef in "Pure Infrastructure-As-Code" Mode?
  • Date: Sun, 24 Jun 2012 20:07:08 +0200

On Sun, Jun 24, 2012 at 12:23 PM, Dan Adams < " target="_blank"> > wrote:

I'm not following you here. It does not do this. Our git commit hook finds only what has changed, and then calculates what needs to be updated based on that. So if you edit an environment file, only the environment file is updated, if you edit a node file, only the node file is updated. The different here is that we don't store nodes as a single JSON file, we use the standard chef git repo structure of node, env, cookbook, client etc files.

Oh, is there a standard place for nodes in the chef repo structure? Didn't know about that, so I added the $CHEF_REPO/nodes directory and placed the node info as .json files (like what you get with `knife node show -fjson`) there...

So your commit hook script would be exactly what I was looking for. +1
for putting it on github :-)

I'm also wondering if other's haven't had the same requirements and
maybe built something similar already?

Yes, I'm sure this is a common requirement and must be written over and over in many shops. I'll upload what I have to github and wait for someone to shoot it down with something far simpler, quicker, more efficient and more elegant :-)

Nice! Two thumbs up! :-)


Archive powered by MHonArc 2.6.16.