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

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

Commit 6b350fb6b75abbe93a8077d52b50eaa93f2d1165 in jclouds's branch 
refs/heads/master from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=6b350fb ]

JCLOUDS-792: Configure chef-client security attributes

This commit also improves some internal behavior related to the
bootstrap configuration generation, and deprecated some methods that
will be removed in upcoming versions.

* Removes all methods that return the bootstrap DataBag or the raw
  configuration json to return the BootstrapConfig object instead.
* Deprecates all methods that provide support for old Chef versions.
* Formats the Enterprise Chef provider according to the jclouds
  formatting guidelines.
* Deprecates the ChefContext view. That view is not an abstraction and
  only provides access to the ChefService. It can be obtained from the
  ChefApi itself.


> Allow to configure the Chef Server certificate
> ----------------------------------------------
>
>                 Key: JCLOUDS-792
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-792
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-chef
>    Affects Versions: 1.8.1
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: chef
>
> Starting from version 12, the Chef client has the SSL verification enabled by 
> default. That makes the current deployments to fail, as the client is not 
> configured with the path to the Chef server certificate to use for validation.
> An option should be added to the {{BootstrapConfig}} object so users can 
> provide the server certificate at config time. This option should be the 
> contents of the certificate file, and the bootstrap process will write it in 
> an appropriate location and configure the Chef client to use that file.



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

Reply via email to