It looks like a bug in the code, have you looked at that provider? It references iam_endpoint[0] but only default_iam_endpoint is defined in that method. If I’m reading it right, you can make it use the right endpoint by setting AWS_IAM_URL.You should open an issue[1], ideally attempt fixing it yourself. The code is open source, you’re welcome to contribute something back.On Monday, October 20, 2014 at 9:41 AM, Douglas Garstang wrote:
No takers? :(
Doug.On Thu, Oct 16, 2014 at 9:00 AM, Douglas Garstang < " target="_blank"> > wrote:Can't get much simpler than that. What am I doing wrong?and here's what I get when I run it:I'm trying to destroy (delete? some docs say it's 'destroy' while other say 'delete') EC2 instances started with chef-metal.Here's the destroy recipe, pretty simple:
require 'chef_metal'
with_chef_server "https://chef01.prod.slicetest.com:443", {
:client_name => Chef::Config[:node_name],
:signing_key_filename => Chef::Config[:client_key]
}
machine "mongo-cfg01.dev-volatile.slicetest.com" do
action :destroy
end
================================================================================
Error executing action `destroy` on resource 'machine[mongo-cfg01.dev-volatile.slicetest.com]'
================================================================================
NameError
---------
undefined local variable or method `iam_endpoint' for ChefMetalFog::Providers::AWS:Class
Resource Declaration:
---------------------
# In /Users/doug/git/chef/chef-metal/mongo-dev-volatile-down.rb
9: machine "mongo-cfg01.dev-volatile.slicetest.com" do
10: action :destroy
11: end
12: #end
Doug
--
Regards,
Douglas Garstang
http://www.linkedin.com/in/garstang
Email: " target="_blank">
Cell: +1-805-340-5627
Archive powered by MHonArc 2.6.16.