Skip to content
Browse files

Fixed incorrect docstring describing use of allocation_id for VPCs

  • Loading branch information...
1 parent 129ec87 commit 7f384610476cc306cd7127c8661e57384897d17a Jerry Jackson committed Jan 9, 2013
Showing with 1 addition and 1 deletion.
  1. +1 −1 lib/ironfan/provider/ec2/elastic_ip.rb
2 lib/ironfan/provider/ec2/elastic_ip.rb
@@ -58,7 +58,7 @@ def!(computer)
return unless computer.created?
# instead of just returning if the elastic_ip is blank we first test if the symbol exists and whether an actual
# address exists in the collection; All three require the presence of elastic_ip in the facet definition. We
- # also, in the absence of an elastic_ip value, can use allocation_id to attach a VPC Elastic IP.
+ # also, in the case of VPC Elastic IPs, can discover and use allocation_id to attach a VPC Elastic IP.
return unless computer.server.ec2.include?(:elastic_ip)
if ( computer.server.ec2.elastic_ip.nil? and cloud.vpc.nil? )
# First, :elastic_ip is set, no address is currently allocated for this connection's owner

0 comments on commit 7f38461

Please sign in to comment.
Something went wrong with that request. Please try again.