zaws 0.0.5 → 0.1.1

data/feature/elasticip/view.feature

@@ -1,18 +0,0 @@
-Feature: Elasticip 
-    
-  Scenario: Get elasticip in a human readable table. 
-    Given I double `aws --output table --region us-west-1 ec2 describe-addresses` with "AWS Elasticip Output" 
-    When I run `bundle exec zaws elasticip view --region us-west-1 --viewtype table`
-    Then the stdout should contain "AWS Elasticip Output\n" 
-
-  Scenario: Get elasticip in a human readable table form by default 
-    Given I double `aws --output table --region us-west-1 ec2 describe-addresses` with "AWS Elasticip Output" 
-    When I run `bundle exec zaws elasticip view --region us-west-1`
-    Then the stdout should contain "AWS Elasticip Output\n" 
-
-  Scenario: Get elasticip in JSON form 
-    Given I double `aws --output json --region us-west-1 ec2 describe-addresses` with "AWS Elasticip JSON Output" 
-    When I run `bundle exec zaws elasticip view --region us-west-1 --viewtype json`
-    Then the stdout should contain "AWS Elasticip JSON Output\n" 
-
-

data/feature/hosted_zone/view.feature

@@ -1,17 +0,0 @@
-Feature: Hosted Zone 
-    
-  Scenario: Get hosted zone in a human readable table. 
-    Given I double `aws --output table route53 list-hosted-zones` with "AWS Hosted Zone Output" 
-    When I run `bundle exec zaws hosted_zone view --viewtype table`
-    Then the stdout should contain "AWS Hosted Zone Output\n" 
-
-  Scenario: Get hosted zone in a human readable table form by default 
-    Given I double `aws --output table route53 list-hosted-zones` with "AWS Hosted Zone Output" 
-    When I run `bundle exec zaws hosted_zone view`
-    Then the stdout should contain "AWS Hosted Zone Output\n" 
-
-  Scenario: Get hosted zone in JSON form 
-    Given I double `aws --output json route53 list-hosted-zones` with "AWS Hosted Zone JSON Output" 
-    When I run `bundle exec zaws hosted_zone view --viewtype json`
-    Then the stdout should contain "AWS Hosted Zone JSON Output\n" 
-

data/feature/hosted_zone/view_record.feature

@@ -1,29 +0,0 @@
-Feature: View Record
-    
-  Scenario: Get records for hosted zone in a human readable table. 
-	Given I double `aws --output json route53 list-hosted-zones` with stdout:
-	"""
-	{   "HostedZones": [  {  "Id": "id-???", "Name": "abc.com." } ] }
-	"""
-	And I double `aws --output table route53 list-resource-record-sets --hosted-zone-id id-???` with "AWS Resource Record Sets Output" 
-    When I run `bundle exec zaws hosted_zone view_records abc.com. --viewtype table`
-    Then the stdout should contain "AWS Resource Record Sets Output\n" 
-
-  Scenario: Get records for hosted zone in a human readable table form by default
-	Given I double `aws --output json route53 list-hosted-zones` with stdout:
-	"""
-	{   "HostedZones": [  {  "Id": "id-???", "Name": "abc.com." } ] }
-	"""
-	And I double `aws --output table route53 list-resource-record-sets --hosted-zone-id id-???` with "AWS Resource Record Sets Output" 
-    When I run `bundle exec zaws hosted_zone view_records abc.com.`
-    Then the stdout should contain "AWS Resource Record Sets Output\n" 
-
-  Scenario: Get records for hosted zone in a JSON form. 
-	Given I double `aws --output json route53 list-hosted-zones` with stdout:
-	"""
-	{   "HostedZones": [  {  "Id": "id-???", "Name": "abc.com." } ] }
-	"""
-	And I double `aws --output json route53 list-resource-record-sets --hosted-zone-id id-???` with "AWS Resource Record Sets Output" 
-    When I run `bundle exec zaws hosted_zone view_records abc.com. --viewtype json`
-    Then the stdout should contain "AWS Resource Record Sets Output\n" 
-

data/feature/load_balancer/instance_registration.feature

@@ -1,120 +0,0 @@
-Feature: Instance Registration 
-    
-  Scenario: Determine instance is registered
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-X" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    When I run `bundle exec zaws load_balancer exists_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "true\n" 
-	
-  Scenario: Determine instance is NOT registered
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-Y" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    When I run `bundle exec zaws load_balancer exists_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "false\n" 
-
-  Scenario: Declare instance registration
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ ] } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    And I double `aws --region us-west-1 elb register-instances-with-load-balancer --load-balancer-name lbname --instances i-X` with stdout:
-     """
-	 { "return" : "true" } 
-	 """
-    When I run `bundle exec zaws load_balancer register_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "New instance registered.\n" 
-
-  Scenario: Declare instance registration, Skip creation
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-X" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    When I run `bundle exec zaws load_balancer register_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "Instance already registered. Skipping registration.\n" 
-
-  Scenario: Delete
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-X" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    And I double `aws --region us-west-1 elb deregister-instances-with-load-balancer --load-balancer-name lbname --instances i-X` with stdout:
-     """
-	 { "return" : "true" } 
-	 """
-    When I run `bundle exec zaws load_balancer deregister_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "Instance deregistered.\n" 
-
-  Scenario: Delete, skip
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ ] } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-	When I run `bundle exec zaws load_balancer deregister_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id`
-	Then the stdout should contain "Instance not registered. Skipping deregistration.\n" 
-	
-  Scenario: Nagios OK
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-X" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    When I run `bundle exec zaws load_balancer register_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the stdout should contain "OK: Instance registerd.\n" 
-
-  Scenario: Nagios CRITICAL
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ ] } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-    When I run `bundle exec zaws load_balancer register_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the stdout should contain "CRITICAL: Instance not registered.\n" 
-
-  Scenario: Undo file
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	 { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "Instances": [ { "InstanceId": "i-X" }  ]} ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-instances --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_instance'` with stdout:
-     """
-	 {  "Reservations": [ { "Instances" : [ {"InstanceId": "i-X","Tags": [ { "Value": "my_instance","Key": "externalid" } ] } ] } ] } 
-	 """
-	Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws load_balancer register_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id --undofile undo.sh.1`
-    Then the stdout should contain "Instance already registered. Skipping registration.\n" 
-	And the file "undo.sh.1" should contain "zaws load_balancer deregister_instance lbname my_instance --region us-west-1 --vpcid my_vpc_id $XTRA_OPTS"
-

data/feature/load_balancer/listener.feature

@@ -1,86 +0,0 @@
-Feature: Listner
-
-  Scenario: Determine listner exists
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 80, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-    When I run `bundle exec zaws load_balancer exists_listener lbname HTTP 80 HTTP 80 --region us-west-1`
-	Then the stdout should contain "true\n" 
-		
-  Scenario: Determine listner does not exist
-	Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 17080, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-    When I run `bundle exec zaws load_balancer exists_listener lbname tcp 80 tcp 80 --region us-west-1`
-	Then the stdout should contain "false\n" 
-
-  Scenario: Declare listner 
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [] } ] }
-     """
-    And I double `aws --region us-west-1 elb create-load-balancer-listeners --load-balancer-name lbname --listeners '[{"Protocol":"HTTP","LoadBalancerPort":80,"InstanceProtocol":"HTTP","InstancePort":80}]'` with stdout:
-	 """
-      { "return": "true" }
-	 """
-    When I run `bundle exec zaws load_balancer declare_listener lbname HTTP 80 HTTP 80 --region us-west-1`
-	Then the stdout should contain "Listener created.\n" 
-		
-  Scenario: Declare listner, Skip creation
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 80, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-    When I run `bundle exec zaws load_balancer declare_listener lbname HTTP 80 HTTP 80 --region us-west-1`
-	Then the stdout should contain "Listerner exists. Skipping creation.\n" 
-		
-  Scenario: Delete
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 80, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-    And I double `aws --region us-west-1 elb delete-load-balancer-listeners --load-balancer-name lbname --load-balancer-ports 80` with stdout:
-	 """
-      { "return": "true" }
-	 """
-    When I run `bundle exec zaws load_balancer delete_listener lbname HTTP 80 HTTP 80 --region us-west-1`
-	Then the stdout should contain "Listerner deleted.\n" 
-	
-  Scenario: Delete, skip
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [] } ] }
-     """
-    When I run `bundle exec zaws load_balancer delete_listener lbname HTTP 80 HTTP 80 --region us-west-1`
-	Then the stdout should contain "Listener does not exist. Skipping deletion.\n" 
-				
-  Scenario: Nagios OK
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 80, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-    When I run `bundle exec zaws load_balancer declare_listener lbname HTTP 80 HTTP 80 --region us-west-1 --nagios`
-	Then the stdout should contain "OK: Listerner exists.\n" 
-	
-  Scenario: Nagios CRITICAL
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [] } ] }
-     """
-    When I run `bundle exec zaws load_balancer declare_listener lbname HTTP 80 HTTP 80 --region us-west-1 --nagios`
-	Then the stdout should contain "CRITICAL: Listener does not exist.\n" 
-	
-  Scenario: Undo file
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-	  { "LoadBalancerDescriptions": [ { "LoadBalancerName": "lbname", "ListenerDescriptions": [ { "Listener": { "InstancePort": 80, "LoadBalancerPort": 80, "Protocol": "HTTP", "InstanceProtocol": "HTTP" }, "PolicyNames": [] } ] } ] }
-     """
-  	Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws load_balancer declare_listener lbname HTTP 80 HTTP 80 --region us-west-1 --undofile undo.sh.1`
-	Then the stdout should contain "Listerner exists. Skipping creation.\n" 
-	And the file "undo.sh.1" should contain "zaws load_balancer delete_listener lbname HTTP 80 HTTP 80 --region us-west-1 $XTRA_OPTS"
-
-
-

data/feature/load_balancer/load_balancer.feature

@@ -1,101 +0,0 @@
-Feature: Load Balancer 
-    
-  Scenario: Determine a load balancer exists in a vpc
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ { "LoadBalancerName": "name-???" } ] }
-     """
-    When I run `bundle exec zaws load_balancer exists name-??? --region us-west-1`
-    Then the stdout should contain "true\n" 
-
-  Scenario: Determine a load balancer does not exist in a vpc
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ ] }
-     """
-    When I run `bundle exec zaws load_balancer exists name-??? --region us-west-1`
-    Then the stdout should contain "false\n" 
-
-  Scenario: Declare load balancer in vpc
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ ] }
-     """
-  	And I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=10.0.0.0/28'` with stdout: 
-     """
-	 { "Subnets": [ { "SubnetId" : "subnet-A???","CidrBlock":"10.0.0.0/28" }] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=10.0.1.0/28'` with stdout: 
-     """
-	 { "Subnets": [ { "SubnetId" : "subnet-B???" ,"CidrBlock":"10.0.1.0/28"}] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter  'Name=vpc-id,Values=my_vpc_id' 'Name=group-name,Values=my_security_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "my_security_group_name","GroupId": "sg-???" } ] }
-     """
-	 And I double `aws --region us-west-1 elb create-load-balancer --load-balancer-name newlb --listeners '[{"Protocol":"tcp","LoadBalancerPort":80,"InstanceProtocol":"tcp","InstancePort":80}]' --subnets subnet-A??? subnet-B??? --security-groups sg-???` with stdout:
-	 """
-      { "DNSName": "???.us-west-1.elb.amazonaws.com" }
-	 """
-	 When I run `bundle exec zaws load_balancer create_in_subnet newlb tcp 80 tcp 80 my_security_group_name --cidrblocks="10.0.0.0/28" "10.0.1.0/28" --vpcid my_vpc_id --region us-west-1`
-    Then the stdout should contain "Load balancer created.\n" 
-
-  Scenario: Declare load balancer in vpc, Skip creation
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ { "LoadBalancerName": "name-???" } ] }
-     """
-    When I run `bundle exec zaws load_balancer create_in_subnet name-??? tcp 80 tcp 80 my_security_group_name --cidrblocks="10.0.0.0/28" "10.0.1.0/28" --vpcid my_vpc_id --region us-west-1`
-    Then the stdout should contain "Load balancer already exists. Skipping creation.\n" 
-
-  Scenario: Delete
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ { "LoadBalancerName": "name-???" }] }
-     """
-   And I double `aws --region us-west-1 elb delete-load-balancer --load-balancer-name name-???` with stdout:
-	 """
-      { "return": "true" }
-	 """
-    When I run `bundle exec zaws load_balancer delete "name-???" --region us-west-1`
-    Then the stdout should contain "Load balancer deleted.\n" 
-
-  Scenario: Delete, skip
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ ] }
-     """
-    When I run `bundle exec zaws load_balancer delete name-??? --region us-west-1`
-    Then the stdout should contain "Load balancer does not exist. Skipping deletion.\n" 
-
-  Scenario: Nagios OK
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ { "LoadBalancerName": "name-???" } ] }
-     """
-    When I run `bundle exec zaws load_balancer create_in_subnet name-??? tcp 80 tcp 80 my_security_group_name --cidrblocks="10.0.0.0/28" "10.0.1.0/28" --vpcid my_vpc_id --region us-west-1 --nagios`
-	Then the output should contain "OK: Load Balancer Exists.\n"
-    And the exit status should be 0
-		  
-  Scenario: Nagios CRITICAL
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ ] }
-     """
-    When I run `bundle exec zaws load_balancer create_in_subnet name-??? tcp 80 tcp 80 my_security_group_name --cidrblocks="10.0.0.0/28" "10.0.1.0/28" --vpcid my_vpc_id --region us-west-1 --nagios`
-	Then the output should contain "CRITICAL: Load Balancer does not exist.\n"
-    And the exit status should be 2
-	
-  Scenario: Undo file
-   Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with stdout:
-     """
-      { "LoadBalancerDescriptions": [ { "LoadBalancerName": "name-???" } ] }
-     """
-	Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws load_balancer create_in_subnet name-??? tcp 80 tcp 80 my_security_group_name --cidrblocks="10.0.0.0/28" "10.0.1.0/28" --vpcid my_vpc_id --region us-west-1 --undofile undo.sh.1`
-    Then the stdout should contain "Load balancer already exists. Skipping creation.\n" 
-	And the file "undo.sh.1" should contain "zaws load_balancer delete name-??? --region us-west-1 $XTRA_OPTS"
-
-    
-
-

data/feature/load_balancer/view.feature

@@ -1,18 +0,0 @@
-Feature: Load Balancer 
-    
-  Scenario: Get load balancer in a human readable table. 
-    Given I double `aws --output table --region us-west-1 elb describe-load-balancers` with "AWS Load Balancer Output" 
-    When I run `bundle exec zaws load_balancer view --region us-west-1 --viewtype table`
-    Then the stdout should contain "AWS Load Balancer Output\n" 
-
-  Scenario: Get load balancer in a human readable table form by default 
-    Given I double `aws --output table --region us-west-1 elb describe-load-balancers` with "AWS Load Balancer Output" 
-    When I run `bundle exec zaws load_balancer view --region us-west-1`
-    Then the stdout should contain "AWS Load Balancer Output\n" 
-
-  Scenario: Get load balancer in JSON form 
-    Given I double `aws --output json --region us-west-1 elb describe-load-balancers` with "AWS Load Balancer JSON Output" 
-    When I run `bundle exec zaws load_balancer view --region us-west-1 --viewtype json`
-    Then the stdout should contain "AWS Load Balancer JSON Output\n" 
-
-

data/feature/route_table/assoc_subnet.feature

@@ -1,128 +0,0 @@
-Feature: Route Table 
-
-  Scenario: Determine that a subnet is associated to a route table 
-	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ { "SubnetId":"X" } ] } ] }
-     """
-    When I run `bundle exec zaws route_table subnet_assoc_exists my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "true\n" 
- 
-  Scenario: Determine that a subnet is NOT associated to a route table 
- 	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ ] } ] }
-     """
-    When I run `bundle exec zaws route_table subnet_assoc_exists my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "false\n" 
-
-  Scenario: Associate a subnet to a route table
- 	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ ] } ] }
-     """
-    And I double `aws --region us-west-1 ec2 associate-route-table --subnet-id X --route-table-id rtb-XXXXXXX` with stdout:
-     """
-	 {	"AssociationId": "rtbassoc-???????" }
-     """
-    When I run `bundle exec zaws route_table assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Route table associated to subnet.\n" 
-
-  Scenario: Associate a subnet to a route table, skip because it exists already
-  	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ { "SubnetId":"X" } ] } ] }
-     """
-    When I run `bundle exec zaws route_table assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Route table already associated to subnet. Skipping association.\n" 
-   
-  Scenario: Delete subnet association to route table
-    Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ { "SubnetId":"X","RouteTableAssociationId":"rtbassoc-????????" } ] } ] }
-     """
-    And I double `aws --region us-west-1 ec2 disassociate-route-table --association-id rtbassoc-????????` with stdout:
-     """
-	 {	"return" : "true" }
-     """
-    When I run `bundle exec zaws route_table delete_assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Route table association to subnet deleted.\n" 
- 
-  Scenario: Delete subnet association to route table that does not exists, skip it.
-	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ ] } ] }
-     """
-    When I run `bundle exec zaws route_table delete_assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Route table association to subnet not deleted because it does not exist.\n" 
-		
-  Scenario: Nagios OK
-  	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ { "SubnetId":"X" } ] } ] }
-     """
-    When I run `bundle exec zaws route_table assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id --nagios`
- 	Then the output should contain "OK: Route table association to subnet exists.\n"
-    And the exit status should be 0
-	
-  Scenario: Nagios CRITICAL
- 	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ ] } ] }
-     """
-    When I run `bundle exec zaws route_table assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id --nagios`
-    Then the output should contain "CRITICAL: Route table association to subnet does not exist.\n"
-    And the exit status should be 2
- 
-  Scenario: Undo file
- 	Given I double `aws --output json --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=cidr,Values=my_cidr_block'` with stdout: 
-     """
-		{ "Subnets": [ { "SubnetId" : "X" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-route-tables --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=tag:externalid,Values=my_route_table'` with stdout:
-     """
-	 {	"RouteTables": [ { "VpcId":"my_vpc_id","RouteTableId":"rtb-XXXXXXX","Associations": [ ] } ] }
-     """
-    And I double `aws --region us-west-1 ec2 associate-route-table --subnet-id X --route-table-id rtb-XXXXXXX` with stdout:
-     """
-	 {	"AssociationId": "rtbassoc-???????" }
-     """
-    Given an empty file named "undo.sh.1"
-    When I run `bundle exec zaws route_table assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id --undofile undo.sh.1`
-    Then the output should contain "Route table associated to subnet.\n" 
-	And the file "undo.sh.1" should contain "zaws route_table delete_assoc_subnet my_route_table my_cidr_block --region us-west-1 --vpcid my_vpc_id"
-
-
-