Update changelog and docs, bump version for release

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Cap-EC2 changelog
 
+## 0.0.15
+
+* Add `ec2_filter_by_status_ok?` to filter out instances that aren't returning `OK` 
+  for their EC2 status checks. [@tomconroy](https://github.com/tomconroy)
+
 ## 0.0.14
 
 * Fix issue when tag was present in EC2 but had no value. [@tomconroy](https://github.com/tomconroy)

README.md

@@ -52,6 +52,8 @@ set :ec2_access_key_id, nil
 set :ec2_secret_access_key, nil
 set :ec2_region, %w{}
 set :ec2_contact_point, nil
+
+set :ec2_filter_by_status_ok?, nil
 ```
 
 #### Order of inheritance
@@ -84,6 +86,11 @@ If running on EC2 the IAM instance profile credentials will be used if credentia
   If this is defined, Cap-EC2 will look for a tag with this name to determine which instances belong to
   a given role. The tag name defaults to "Roles".
 
+* filter_by_status_ok?
+
+  If this is set to `true`, then Cap-EC2 will not return instances which do not have both EC2 status
+  checks as `OK`. By default this is set to `nil`, so Cap-EC2 can return you instances which don't have
+  `OK` status checks. Be warned that just-launched instances take a while to start returning `OK`.
 
 ### YAML Configuration
 

lib/cap-ec2/version.rb

@@ -1,3 +1,3 @@
 module CapEC2
-  VERSION = '0.0.14'
+  VERSION = '0.0.15'
 end