Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
1.6.2, 1.7.0
-
N/A
Description
From e-mail conversation
From: Ignasi <ignasi.barrera@gmail.com>
Subject: Re: [jclouds-chef] Support for Chef server 11
To: Noorul Islam K M <noorul@collab.net>
Date: Wed, 28 Aug 2013 11:10:49 +0200 (17 hours, 56 minutes, 55 seconds ago)
It is not intentional if there are some missing apis. We added the
environment API time ago [1], but not all endpoints were added then,
and are still missing.
Mind opening an Improvement in JIRA to add the missing ones?
Also, if you want to contribute them [2], that would be very welcome!
I plan to merge JCLOUDS-246 as it might block contributions (due to
the change of the project structure).
Ignasi
[1] https://github.com/jclouds/legacy-jclouds-chef/pull/61
[2] https://wiki.apache.org/jclouds/How%20to%20Contribute
On 28 August 2013 11:03, Noorul Islam K M <noorul@collab.net> wrote:
[-]
> Ignasi <ignasi.barrera@gmail.com> writes:
>
>> Hi Noorul,
>>
>> Finally, I've fixed the issue! Here is the commit [1] that fixes
>> it. Basically we don't have to encode the '+' and ' ' characters in
>> the Signature query parameter. With this fix applied, all live tests
>> are passing for Chef 0.10, Chef 11 and Enterprise Chef.
>>
>> Feel free to checkout my branch [2] and validate the live tests
>> (specially the testDownloadCookbooks).
>>
>
> Thanks a lot!
>
> I see that some of the APIs are not exposed, for example
>
> http://docs.opscode.com/api_chef_server_environments_recipe.html
>
> Is this something that consciously avoided?
>
> Thanks and Regards
> Noorul
>