- From: Alex Soto <
>
- To: "
" <
>
- Cc: "
" <
>
- Subject: [chef] Re: Problem with chef-solo
- Date: Sat, 27 Feb 2010 11:08:15 -0800
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=references:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:x-mailer:mime-version:subject:date:cc; b=Wa1Q9LfEesKzKpdlYsD5RYWqUkGCMMG5XVMWYkqMdu+r9msGakKWsGFmmWuWz21iwc SmzUkYfUIA4Q0YTgHIzlO8xU9U73A0rUikj6pMKzWpEV7qidEiVvO0K42cDZldOt4tEq 0A8G2DHpTvi3S37duX8NsxJWOD7gN1XhJbyJg=
Chef solo doesn't communicate with a remote server. Therefore any
changes on the server have no affect. Use chef client if you want
remote changes to be reflected on the node.
Sent from my phone
On Feb 27, 2010, at 6:58 AM, Jeppe Nejsum Madsen <
>
wrote:
Hi,
I'm currently only using chef-solo for deployment and found an issue:
It seems chef-solo doesn't clear the cookbook directory before
unpacking
the new cookbook retrieved via http.
This means if a file is removed from e.g. site-cookbooks in the remote
bundle, it will not be removed before chef-solo runs.
Should I file a ticket for this?
/Jeppe
Archive powered by MHonArc 2.6.16.