- From: Gilles Devaux <
>
- To:
- Subject: [chef] Re: changing the repository in SCM resource
- Date: Wed, 8 Sep 2010 09:55:02 -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=nbm5weZnqalMfeY9RT/g4nIOrlLuLL6z0/7kIr8eGLcZekT7NoYL0aT59CnTOGH/CM Soi+SipTibzen7UFhh4KXETyO1s7GMHGQDj6VgNhODTWu0PNd6GgQGeF4z6tjhOPX0/l NXbNkW/2y1MYEAnJke48ihSTAsMAfIQbnDwzs=
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
On Wed, Sep 8, 2010 at 12:29 AM, Dmitry V'yal
<
>
wrote:
>
Hello,
>
>
I have a following question. I deployed a bunch of scripts from several git
>
repositories using an SCM resource to a number of workstations. Now I need
>
to move some of repositories. I updated the repository attribute of my
>
resources to point to new locations, but chef-0.9.6 seems to ignore the
>
changes and tries to sync using old uri.
>
>
One solution is to delete the deployed repositories and run chef-client to
>
deploy them afresh. I sure there must be a better way. Folks?
>
>
Thanks in advance,
>
Dmitry
>
Archive powered by MHonArc 2.6.16.