- From: Xabier de Zuazo <
>
- To:
- Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Berksfile.lock commit in dev branches
- Date: Tue, 17 Feb 2015 12:38:36 +0100
Ohai Torben!
On Tue, Feb 17, 2015 at 07:16:46AM +0100, Torben Knerr wrote:
>
[...]
>
I know that berkshelf is included in the ChefDK, but I believe it's not
>
included in the omnibus chef client. So not sure if that plays well
>
together, but it should as chef client only looks at the generated
>
metadata.json, right?
That's a good point, as you say omnibus chef-client does not include
berkshelf.
CMIIW but I think chef-client ignores all the metadata files. It uses the
metadata field in the JSON data returned by the Chef Server. This metadata
contains the temporal "metadata.json" file content generated in the
knife/berks
upload process.
So, more or less yes, chef-client only looks at the "metadata.json".
Cheers,
--
Xabier de Zuazo
Attachment:
signature.asc
Description: Digital signature
- [chef] Re [2]: Re [2]: Can't bootstrap windows node after upgrading to ChefDK v4. (Please help! Windows platform), (continued)
[chef] Re: Re: Re: Berksfile.lock commit in dev branches, William Jimenez, 02/13/2015
[chef] Re: Re: Re: Berksfile.lock commit in dev branches, Xabier de Zuazo, 02/14/2015
Archive powered by MHonArc 2.6.16.