[chef] knife upload cookbook dependencies?


Chronological Thread 
  • From: Dreamcat4 < >
  • To:
  • Subject: [chef] knife upload cookbook dependencies?
  • Date: Sun, 7 Nov 2010 13:37:31 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=xQrREomlrEfwDsnV9RcfJ4SyhHkj52j6k3zs/iJE6/AKU7Z9iFIuZKG7ryhf9BkmO0 GackfhxPe0UyU25EwkkpLG0XpXd/QKG+xCxKnYhzM8C13GtgNyQEX88ghuJTbEXXzNBH 4WdLBH3Sv2RkWjQse7WlyERq+m9xrzA4e7I9c=

Hi,
I'm aware that many people just upload everything, all of their
cookbooks. However in my case theres simply far too many of them.
So...

Any reason we cant have a '-d' flag for uploading cookbooks?

It seems knife site vendor already knows how to iterate over the
cookbook dependencies. Im thinking perhaps that can be leveraged for
the cookbook uploading too.

For example

knife cookbook site vendor COOKBOOK -d
knife cookbook site vendor COOKBOOK --dependencies

Would become

knife cookbook upload vendor COOKBOOK -d
knife cookbook upload COOKBOOK --dependencies

I'd be happy to have a crack at it.


dreamcat4




Archive powered by MHonArc 2.6.16.

§