[chef] Re: Re: Is it possible to version control Chef Repository when working from management workstation?

[Joshua Miller < >]

The real problem in your example is to get away from commands like

knife data bag edit 
And 
knife role edit 

Use the chef-repo example and have roles and data bags in there.  Edit the 
roles locally and then use standard source control options.  When your ready 
to push to the chef server use the from file commands.

knife data bag from file users jmiller.json

knife role from file base.json

Hope that helps



On Jul 5, 2012, at 9:54 AM, Adam Jacob 
<
 >
 wrote:

> You commit before you run knife, or you run the knife commands as a
> post-commit hook.
> 
> Best,
> Adam
> 
> On Thu, Jul 5, 2012 at 5:51 PM, anatoly techtonik 
> <
 >
>  wrote:
>> Hi,
>> 
>> I work with Chef from workstation knife. I thought that I need to
>> clone Chef Repository, work with my local copy and then sync it with
>> the server. But it appears knife modifies that most things (like data
>> bags) directly on server through API not giving me a chance to record
>> the changes by committing them into version control system of my local
>> copy.
>> 
>> So basically if I want a version control over my configuration (Chef
>> Repository) I am limited to committing changes from server side only.
>> Did I miss something? How do people version control their
>> configuration?
>> 
>> It could help if knife had command to download the whole repo.
>> --
>> anatoly t.
> 
> 
> 
> -- 
> Opscode, Inc.
> Adam Jacob, Chief Customer Officer
> T: (206) 619-7151 E: 
>