No :access_key_id provided (AWS::ArgumentError)

[Brandon Casci]

I'm taking the newest rubber out for a test drive. I've configured rubber.yaml correctly, but it looks like the AWS access key isn't getting picked up. Any ideas?

brandon@dell-desktop:~/projects/rails_apps/loudcaster_new$ cap -T
/usr/lib/ruby/gems/1.8/gems/amazon-ec2-0.5.5/lib/AWS.rb:115:in `initialize': No :access_key_id provided (AWS::ArgumentError)
    from /usr/lib/ruby/gems/1.8/gems/wr0ngway-rubber-1.0.1/lib/rubber/cloud/aws.rb:13:in `new'
    from /usr/lib/ruby/gems/1.8/gems/wr0ngway-rubber-1.0.1/lib/rubber/cloud/aws.rb:13:in `initialize'
    from /usr/lib/ruby/gems/1.8/gems/wr0ngway-rubber-1.0.1/lib/rubber/cloud.rb:9:in `new'
    from /usr/lib/ruby/gems/1.8/gems/wr0ngway-rubber-1.0.1/lib/rubber/cloud.rb:9:in `get_provider'
    from /usr/lib/ruby/gems/1.8/gems/wr0ngway-rubber-1.0.1/lib/rubber/recipes/rubber.rb:52:in `load'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:128:in `instance_eval'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:128:in `invoke_task_directly_without_callbacks'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/callbacks.rb:27:in `invoke_task_directly'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:81:in `execute_task'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/execution.rb:93:in `find_and_execute_task'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/callback.rb:38:in `call'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/callbacks.rb:128:in `trigger'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/callbacks.rb:128:in `each'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/configuration/callbacks.rb:128:in `trigger'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:32:in `execute!'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/lib/capistrano/cli/execute.rb:14:in `execute'
    from /usr/lib/ruby/gems/1.8/gems/capistrano-2.5.5/bin/cap:4
    from /usr/bin/cap:19:in `load'
    from /usr/bin/cap:19



--
=========================================
I'm having a bout of spondylosis, so I can't hammer away at the keyboard too long. Please don't mistake short e-mails for rude e-mails..
=========================================

[Brandon Casci]

upon CAREFUL inspection of rubber.yml....I found a mangled key name....oops!

[Matthew Conway]

Heh, yup, been there.

Also, I notice from your stack trace that you are using a slightly older version of rubber.  You probably should "gem install rubber" from gemcutter because thats where the canonical version is now (v1.1.4).  Probably a good idea to gem uninstall the wr0ngway-rubber gem as well so you don't get any weird conflicts.  You can also still use it as a vendored plugin if you prefer.

[Brandon Casci]

Ok...just installed gemcutter and made it my default gem repo. I noticed rubber.yml uses the github version of the gem. Do you recommend I make it use gem cuttter as well?

[Matthew Conway]

The stock rubber.yml uses just "rubber" as the gem and has gemcutter
as a source. Did you re-vulcanize with the new version of rubber?

[Brandon Casci]

It was vulcanzied with the wr0ngway-rubber gem....whihc was rubber 1.0.1 I think.

[Matthew Conway]

Yes, if you use the github gem, it refers to itself, likewise, the gemcutter gem refers to itself.  You should just use the gemcutter one and revulcanize with it

Matt

[Brandon Casci]

Ok....done! I still have the same security group issue I mentioned in the other post, even after vulcanizing again.

[Matthew Conway]

Can you file a issue on the github project? Thanks,

Matt

[Brandon Casci]

sure, done.