General discussion about Chef

[chef] Re: Re: Re: changing the repository in SCM resource


Chronological Thread 
  • From: Paul Paradise < >
  • To:
  • Subject: [chef] Re: Re: Re: changing the repository in SCM resource
  • Date: Sun, 12 Sep 2010 10:07:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=t6QEk1J8d6lRYCvdYbqOrXrxMDUdhIvhzB5jrSaBaWk3FWaqEm4aVFpmcLaBKOf+uP T9pzIeI4+lNl4Ur9yrlssq+y3He1BAx0I9jWdQ02GOJfyMA/WHngh90vJYbukrp/5MMi xobgcy5fwJLgGycG+qZhBOB1yhPE2UFkrVZKQ=
On Sun, Sep 12, 2010 at 3:29 AM, Dmitry V'yal < "> > wrote:
On 08.09.2010 20:55, Gilles Devaux wrote:
Yo,

How did you update the attributes? If you used 'default' then chef
will not change a node's attribute if it's already there:
http://wiki.opscode.com/display/chef/Attributes

--Gilles

well, by attributes I mean atributes of the scm resource, like here:

scm tool do
   destination "#{node[:tools][:prefix]}/#{tool}"
   repository "#{node[:tools][:repo]}/#{tool}"
   action :sync
   provider "git"
end

looks like chef doesn't make sure the git remote of a cloned repo matches the repository attribute provided. Is it a feature?

For the git provider, there was already a bug:


I just cloned the bug for Subversion as http://tickets.opscode.com/browse/CHEF-1662, but I don't have access to edit bug descriptions so someone with more access than me might want to edit that...

-Paul

Archive powered by MHonArc 2.6.16.

§