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

ASF subversion and git services commented on JCLOUDS-245:
---------------------------------------------------------

Commit 3f2a196f269727faea732806807ea04043ca9126 in branch refs/heads/master 
from [~nacx]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds-chef.git;h=3f2a196 ]

JCLOUDS-245/JCLOUDS-254: Fix live tests

Refactored the domain model to be immutable and addressed some
inconsistences with the Chef Server API model.

Removed all HEAD methods, as they have been removed from newer versions
of Chef. They were used to test the existance of a given resource, and
with newer versions the only way to do that is via a GET operation.

Now all live tests are passing for Community Chef 0.10.8, 11.0.6 and
Enterprise Chef.

                
> Review HostedChef api changes to make live tests pass again
> -----------------------------------------------------------
>
>                 Key: JCLOUDS-245
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-245
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-chef
>    Affects Versions: 1.6.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: hostedchef
>         Attachments: JCLOUDS-254-254.patch
>
>
> Hosted Chef API seems to have changed a bit, and now there are several 
> methods that don't allow the HEAD verb. Using the version header has also no 
> effect, so there is no way to force the old behavior (even when the API docs 
> say it is possible).
> A general review of the api and live tests should be performed, taking 
> special care of:
> * The problematic HEAD methods should be refactored to perform a GET 
> operation.
> * The cookbook parsing and construction should be also reviewed as some 
> fields have become mandatory in the latest version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to