[ 
https://issues.apache.org/jira/browse/BROOKLYN-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149011#comment-14149011
 ] 

ASF GitHub Bot commented on BROOKLYN-70:
----------------------------------------

GitHub user ahgittin opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/190

    fix BROOKLYN-70 , allowing the new-style chef community download links

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ahgittin/incubator-brooklyn chef-download-link

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/190.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #190
    
----
commit 9667fa8df33dc94099188f8c1228c0595a778876
Author: Alex Heneveld <[email protected]>
Date:   2014-09-26T10:39:30Z

    fix BROOKLYN-70 , allowing the new-style chef community download links

----


> new chef community site uses different download links not compatible with 
> brooklyn-chef support
> -----------------------------------------------------------------------------------------------
>
>                 Key: BROOKLYN-70
>                 URL: https://issues.apache.org/jira/browse/BROOKLYN-70
>             Project: Brooklyn
>          Issue Type: Bug
>            Reporter: Alex Heneveld
>
> it used to be that the preferred URL was the github release, e.g.
>     (1) https://github.com/poise/poise/archive/v1.0.10.tar.gz
> now they seem to offer a convenience link at
>     (2) https://community.opscode.com/cookbooks/poise/versions/1.0.10/download
> which redirects to a CDN:
>     (3) 
> https://s3.amazonaws.com/community-files.opscode.com/cookbook_versions/tarballs/6179/original/poise.tgz?1394831504
> WORKAROUND
> until we support this new chef community mechanism (which will require some 
> work, because we have to be smarter about how we unpack the archive), instead 
> of using (2) above users should follow the "View Source" link to github then 
> the "<#> Releases" link and get the github TGZ for the recipe(s) desired.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to