On Fri, Jan 17, 2014 at 2:09 PM, Daniel DeLeo email@example.com wrote:
Sounds like a bug, can you create a ticket for it?
On Friday, January 17, 2014 at 10:31 AM, Christopher Armstrong wrote:
Ah. There may be no silver bullet for that.
On Fri, Jan 17, 2014 at 10:29 AM, Dave Konopka firstname.lastname@example.org:
Wouldn’t that ignore the frozen flag for all cookbooks?
I want to prevent changes where the cookbook version has not changed and
allow changes where the version has been bumped.
On Fri, Jan 17, 2014 at 1:23 PM, Christopher Armstrong <
Have you tried adding --force ? This should force the upload even though
some are frozen.
On Fri, Jan 17, 2014 at 6:13 AM, Dave Konopka email@example.com:
Is there anyway with knife to upload all cookbooks from a monolithic
cookbook repo after freezing cookbooks?
Our deploy process is to run
knife cookbook upload --all from the repo.
I did some experimenting with a Chef 11 server vm. After freezing all
knife cookbook upload --all fails on the first cookbook
being frozen even though nothing has changed with it. Later legitimate
changes in other cookbooks in the repo are not saved on the server.
Looking at the knife code, it looks like files are selectively uploaded
based on whether or not they have changed. But then a save is fired for
all cookbooks regardless of whether not they have changed.
Splitting up the repo is on our agenda but at the moment we’re working
with what we have.