Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong digitalocean_client_id when drivers is used in knife.rb #36

Open
szymonpk opened this issue Feb 21, 2015 · 1 comment
Open

Wrong digitalocean_client_id when drivers is used in knife.rb #36

szymonpk opened this issue Feb 21, 2015 · 1 comment

Comments

@szymonpk
Copy link

I'm not sure which gem's fault this is but story is I'm setting up cluster with chef-provisioning, my knife.rb is:

drivers({
  'fog:DigitalOcean:staging' => {
    :driver_options => {
      :compute_options => {
        :digitalocean_api_key => '<hash>',
        :digitalocean_client_id => '<hash>'
      }
    }
  }
})

I've also proper profile defined I'm running chef-client and I'm receiving '401 Unauthorized' from DO. chef-provisioning-fog is using Cheffish to get result config, extracts client_id and api_key.

result = Cheffish::MergedConfig.new(new_config, config, new_defaults)
...
id = result[:driver_options][:compute_options][:digitalocean_client_id]

When I'm running inspect on result[:driver_options] I'm getting:

#<Cheffish::MergedConfig:0x007fe81fc63bf8 @configs=[{:compute_options=>{:provider=>"DigitalOcean", :digitalocean_client_id=>"staging"}}, {:compute_options=>{:digitalocean_api_key=>"<hash>", :digitalocean_client_id=>"<hash>"}}, {:compute_options=>{}}], @merge_arrays={}>

my driver id is used as 'digitalocean_client_id'. It should be digital_client_id hash.

@jkeiser jkeiser added this to the 1.0 milestone Mar 2, 2015
@lamont-granquist lamont-granquist removed this from the 1.0 milestone Dec 7, 2016
@lamont-granquist
Copy link
Contributor

Difficult to determine what the problem is without a lot of work setting up a replication case. Marking this as "Low" due to the narrow scope, effort involved in replicating, and hope that paving over Cheffish::MergedConfig with a proper Chef::Mash will make it disappear...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants