[chef] Re: Re: Re: Re: Re: Re: Re: Re: Question about uploading cookbooks

[JJ Asghar < >]

Wow, pretty slick Kevin.

I’ll give this a shot :) Thanks!

Best Regards,

JJ Asghar

e: | c: 512.619.0722 | o: 512.977.5876

From: Kevin Nuckolls < "> >
Reply-To: " "> " < "> >
Date: Wednesday, March 26, 2014 at 6:57 PM
To: chef < "> >
Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Question about uploading cookbooks

If all of your cookbooks are being uploaded by knife you can use my knife wrapper, knife-santoku[1], to run arbitrary code before or after knife commands. It'll let you define a regexp that matches against knife commands so you can for example fire off a notification whenever anyone uses a command with "upload" in it. 

My current philosophy is that all cookbook uploads should be done via CI and now that I upload cookbooks largely with berks upload this tool has become less useful to me. Regardless, my original intent was to add callbacks to knife commands and knife-santoku will do that exceedingly well. If you generalize your knife configuration to be entirely environment variable driven you can go the extra mile and standardize how your team uses knife with a standard set of santoku callbacks. I've also used this to discourage the use of "knife environment edit" in the past.

Hope that helps,
-Kevin

[1] https://github.com/knuckolls/knife-santoku

On Wed, Mar 26, 2014 at 2:47 PM, JJ Asghar < " target="_blank"> > wrote:

Thanks Julian,
I opened https://tickets.opscode.com/browse/CHEF-5156

I don’t expect this to be resolved in the near future, but hopefully we’ll
get some eyes on it :)

Best Regards,
JJ Asghar
e: "> | c: 512.619.0722 | o: 512.977.5876

On 3/26/14, 11:32 AM, "Julian C. Dunn" < "> > wrote:

>Sure, go ahead!
>
>- Julian
>
>On Wed, Mar 26, 2014 at 12:31 PM, JJ Asghar < "> >
>wrote:
>> Yeah, that's what I was thinking, either figure out the log entry and
>>have
>> splunk send out an alert, or dig into the core code.
>>
>> Julian, any chance I can open a feature request for this? I'm assuming
>> "chef" project on jira?
>>
>>
>> Best Regards,
>> JJ Asghar
>> e: "> | c: 512.619.0722 | o: 512.977.5876
>>
>>
>>
>>
>>
>> On 3/26/14, 11:26 AM, "Julian C. Dunn" < "> > wrote:
>>
>>>It is tricky. There are no handlers that run on the server itself.
>>>However, since the REST requests are captured in the nginx logs, you
>>>could potentially do something with that (send the logs to logstash or
>>>something and alert on that)
>>>
>>>Beyond that, you're probably at looking at hacking Chef server core...
>>>
>>>- Julian
>>>
>>>On Wed, Mar 26, 2014 at 12:21 PM, JJ Asghar < "> >
>>>wrote:
>>>> Oh whoops, I meant Open source chef server.
>>>>
>>>>
>>>> Best Regards,
>>>> JJ Asghar
>>>> e: "> | c: 512.619.0722 | o: 512.977.5876
>>>>
>>>>
>>>> From: Ranjib Dey < "> >
>>>> Reply-To: " "> " < "> >
>>>> Date: Wednesday, March 26, 2014 at 11:09 AM
>>>> To: " "> " < "> >
>>>> Subject: [chef] Re: Question about uploading cookbooks
>>>>
>>>> i think you can click the follow button on community cookbook side,
>>>>and
>>>>then
>>>> you will be emailed whenever a new version comes. But this is per
>>>>cookbook.
>>>> I think supermarket also has some features for the same,
>>>>
>>>>
>>>> On Wed, Mar 26, 2014 at 8:48 AM, JJ Asghar < "> >
>>>> wrote:
>>>>>
>>>>>
>>>>> Is there a way to have Open source chef announce when someone has
>>>>>uploaded
>>>>> a cookbook? Something like a handler seems like a good idea.
>>>>>
>>>>> I'm betting it would be tricky with the way chef is right now, but I
>>>>> thought I might ask.
>>>>>
>>>>>
>>>>> Best Regards,
>>>>> JJ Asghar
>>>>> e: "> | c: 512.619.0722 | o: 512.977.5876
>>>>>
>>>>
>>>
>>>
>>>
>>>--
>>>[ Julian C. Dunn < "> >          * Sorry, I'm    ]
>>>[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
>>>[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
>>>[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]
>>
>
>
>
>--
>[ Julian C. Dunn < "> >          * Sorry, I'm    ]
>[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
>[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
>[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]