wbailey / claws Goto Github PK

Right now every time you run the tool it queries AWS to get the results. It might be wise to add a command line flag that indicates that it should cache the results locally. A corresponding flag value would invalidate the cache.

When I run

claws -d

I get one of these error message per instance:

/home/jamie/.rvm/gems/ruby-1.8.7-p302@jamie/gems/claws-1.1.0/lib/claws/report/ec2.rb:44: warning: Object#id will be deprecated; use Object#object_id

Looking at the claws output from run to run the value for ID changes and is not an EC2 instance ID, which is of the form i-12345678 but is instead a Ruby object ID. Editing .claws.yml and changing the id field from

id:
  title: ID
  width: 10

to

instance_id:
  title: ID
  width: 10

Fixes the problem.

The documentation for amazon-sdk indicates that the instance ID can be accessed via "#id" or "#instance_id".

Thanks,

Jamie

C:\Users\pmjs>claws
undefined method inject' for #<String:0x248a078> C:/Ruby193/lib/ruby/gems/1.9.1/gems/claws-1.2.0/lib/claws/report/ec2.rb:29:inb
lock in run': undefined method each' for nil:NilClass (NoMethodError) from C:/Ruby193/lib/ruby/gems/1.9.1/gems/command_line_reporter-3.2.1/lib /command_line_reporter.rb:118:intable'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/claws-1.2.0/lib/claws/report/ec
2.rb:16:in run' from C:/Ruby193/lib/ruby/gems/1.9.1/gems/claws-1.2.0/lib/claws/command/e c2.rb:19:inexec'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/claws-1.2.0/bin/claws:13:in <t op (required)>' from C:/Ruby193/bin/claws:23:inload'
from C:/Ruby193/bin/claws:23:in `

After installation, claws is not showing instances present in Sao Paulo datacenter. Not tested in other regions to check if it's only there.

Ability to use mosh http://mosh.mit.edu/ instead of plain SSH for remote login, this would be a nice feature, I use mosh instead of plain SSH in most of my EC2 servers