Hi! TL;DR
- The enterprisechef provider disappears and the chef api gets an optional api with its features. - Default Chef api version is upgraded to Chef 12. --- I've opened #874 [1] to join the enterprisechef provider and the chef api. Starting from Chef 12, there is only one version of the Chef Server and it is entirely open source. This makes unnecessary to have two providers for the same thing. The PR moves the apis in the enterprisechef provider to the chef api, but since they are only available since Chef 12 (or in the hosted chef version), they are marked Optional. jclouds will take care of returning them accordingly depending on the version of the Chef Server. The ChefApi will now expose the following method to access the specific hosted chef and Chef 12 features: Optional<OrganizationApi> organizationApi(); Regarding the hosted service, it still exists, but it is consumed as an api: there are no sensible defaults or different APIs in there, and the endpoint can't be preconfigured because the user's organization is part of the url. There is nothing to preconfigure, so it does not make sense to maintain the hosted chef provider. [1] https://github.com/jclouds/jclouds/pull/874
