I am getting an warning when using DeployKeyGithub as it is show in the documentation.

"WARN: Using an LWRP provider by its name (DeployKeyGithub) directly is no longer supported in Chef 12 and will be removed. Use Chef::ProviderResolver.new(node, resource, action) instead."

I am not certain if this is an issue in the examples in the documentation or in the cookbook code.

Which token are we supposed to use with Bitbucket? Currently I'm using username/password, and using the API key as the password.

I've a git repository hosted in bitbucket and I'm writing a recipe to clone the recipe suing 'deploy_key' and 'git' resource as mentioned below.

deploy_key "bitbucket_key" do
provider Chef::Provider::DeployKeyBitbucket
path 'C:\Windows\Temp'
credentials({
:user => 'my_user',
:password => "my_passowrd"
})
repo 'account/repo.git'
action :add
end

git "C:\ABC" do
repository "[email protected]:account/repo.git"
user "my_user"
action :checkout
end

While deploying recipe I'm getting following error.

Recipe Compile Error in

c:/chef/cache/cookbooks/deploy_key/libraries/deploy_key.rb

Gem::LoadError

Unable to activate httparty-0.12.0, because json-1.7.7 conflicts with json (~>
1.8)

Cookbook Trace:

c:/chef/cache/cookbooks/deploy_key/libraries/deploy_key.rb:22:in `<top
(required)>'

Environment detail:
OS: Windows 2012

Hi, currently this cookbook creates 1 pub/private key per repo. Here I'm doing:

  %w[org/project1 org/project2].each do |repo|
    deploy_key repo.split('/')[1] do
      provider Chef::Provider::DeployKeyBitbucket
      path '/home/classcraft/.ssh'
      credentials({ user: 'my_user', password: 'MY_KEY' })
      repo repo
      owner 'my_user'
      group 'my_group'
      action :add
    end
  end

It seems that git is confused about the fact that it now has two keys. Why do you create a key per repo? Should we not create just 1 key and always upload that one?

This was reported on the Chef mailing list.

I'm using deploy_key resource to upload ssh key and then using git resource to
clone the repository. I'm getting below mentioned compilation error.

================================================================================
Recipe Compile Error in
c:/chef/cache/cookbooks/deploy_key/libraries/deploy_key.rb
================================================================================

Gem::LoadError
--------------
Unable to activate httparty-0.12.0, because json-1.7.7 conflicts with json (~>
1.8)

Cookbook Trace:
---------------
c:/chef/cache/cookbooks/deploy_key/libraries/deploy_key.rb:22:in `<top
(required)>'

Here is how my recipe looks like.

deploy_key "bitbucket_key" do
  provider Chef::Provider::DeployKeyBitbucket
  path 'C:\Windows\Temp'
  credentials({
    :user => 'my_user',
    :password => "my_passowrd"
  })
  repo 'organization/repo/path'
  action :add
end

git "C:\\ABC" do
  repository "https://bitbucket.org/organization/repo/path"
  user "my_user"
  action :checkout
end

I am experiencing a very odd issue with the deploy_key resource. When I provide the name ads_dev-chef-ads1_deploy_key my keys are generated but empty. The files appear, but nothing is in them.

I have appended a single character to the file name and it works. But remove that character and you get empty files.

-rw------- 1 kpdev kpdev 1675 May 19 00:10 aads_dev-chef-ads1_deploy_key
-rw------- 1 kpdev kpdev  382 May 19 00:10 aads_dev-chef-ads1_deploy_key.pub
-rw------- 1 kpdev kpdev    0 May 19 00:07 ads_dev-chef-ads1_deploy_key
-rw------- 1 kpdev kpdev    0 May 19 00:07 ads_dev-chef-ads1_deploy_key.pub

I have removed the cache, deleted the whole ~/.ssh/ folder and the results are always the same. I have even gone so far as to manually run the command and it works.

ssh-keygen -t rsa -q -C '' -f '/home/kpdev/.ssh/ads_dev-chef-ads1_deploy_key' -P "" produces the appropriate output, but not through cookbook-deploy_key