On 08.09.2010 20:55, Gilles Devaux wrote:
How did you update the attributes? If you used ‘default’ then chef
will not change a node’s attribute if it’s already there:
well, by attributes I mean atributes of the scm resource, like here:
scm tool do
looks like chef doesn’t make sure the git remote of a cloned repo
matches the repository attribute provided. Is it a feature?
On Wed, Sep 8, 2010 at 12:29 AM, Dmitry V’email@example.com wrote:
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,