[chef] Re: Re: Re: Re: looks_like_ec2? fallback gist

[AJ Christensen < >]

I guess this shows Opscodes perspective vs. some random dude in the
community quite well; props for replying at the same time.

--AJ

On 22 February 2012 09:44, Bryan McLellan 
<
 >
 wrote:
> On Tue, Feb 21, 2012 at 3:32 PM, Hedge Hog 
> <
 >
>  wrote:
>> Possibly, apologies for this but I don't really hunt in opscode's bug
>> database too much anymore - from memory I do have an account (for a
>> different role) I could use.  Simple reason is that, if you are
>> serious about participating in squashing a bug, it is too frustrating
>> to encounter this sort of thing[0], ironic that there is an example of
>> this in the bug you cite.
>>
>> For the moment I find it suffices to google for people publishing
>> gists/workarounds - just like this :)
>>
>> [0]: 
>> http://tickets.opscode.com/browse/OHAI-310?focusedCommentId=21505&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-21505
>
> Yeah, that sucks sometimes, sorry dude. The tickets in the Opscode
> support system can be a great help because they contain good
> information to reproduce the problem, but sometimes the user makes
> them private to protect sensitive data in there, then only the user
> and Opscode can see the ticket. Maybe I could add a filter to hide
> those comments on JIRA from non-opscode employees.
>
> But still, there is no shortage of other people participating directly
> on that ticket. I consider JIRA to be the central authority on all
> Chef bugs (which is why even Opscode support tickets get linked back
> there). It's really nice when you're working with the code and you can
> review the history and discussion of the problem in one place, which
> is admittedly different from just looking for a workaround on the
> interweb.
>
> Bryan