- From: "Stewart, Curtis" <
>
- To: "
" <
>
- Subject: [chef] Re: To Freeze or Not to Freeze
- Date: Tue, 13 May 2014 13:56:02 +0000
- Accept-language: en-US
- Authentication-results: spf=none (sender IP is )
;
Thanks for the reply, Pete!
Is your upload/freeze process done manually via ‘knife-cookbook-upload —freeze”? Or do you use something like Berkshelf or knife-spork for cookbook uploading?
Curtis Stewart
Consultant
m 217.390.5067
Skype cstewart8710
Cloud Migration - Architecture - DevOps - Big Data - App Dev
On May 13, 2014, at 8:38 AM, Pete Cheslock <
">
> wrote:
I would freeze on every upload by default. I would not want a cookbook with the same version but with a change get uploaded to the server and break something. We use pinned versions in our environment files so that ensure that environment must change
for the change to be applied.
-Pete
On May 13, 2014, at 9:32 AM, "Stewart, Curtis" <
">
> wrote:
How do most folks determine when a cookbook should be frozen? Or even whether or not to freeze them at all. Is it once a cookbook is used in a deployment? Or, is it every time a cookbook is uploaded to the server?
Thanks,
Curtis
Curtis Stewart
Consultant
m 217.390.5067
Skype cstewart8710
|
Archive powered by MHonArc 2.6.16.