zaws 0.0.5 → 0.1.1

data/feature/security_group/ingress_group.feature

@@ -1,184 +0,0 @@
-Feature: Security Group 
-  Security Group(s) are viewable
-    
-   Scenario: Determine a vpc securiry group ingress group rule identified by source and target has NOT been created
-	Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-      {	"SecurityGroups": [] }
-     """
-    When I run `bundle exec zaws security_group ingress_group_exists target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "false\n" 
-
-   Scenario: Determine a vpc security group ingress group rule identified by source and target has been created
-	Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-	 {	"SecurityGroups": [ { 
-	        "GroupName": "target_group_name",
-			"GroupId": "X_target_group_name",
-			"IpPermissions": [ {
-				  "ToPort": 443,
-				  "IpProtocol": "tcp",
-				  "IpRanges": [],
-				  "UserIdGroupPairs": [ {
-					 "UserId": "958601521864",
-					 "GroupId": "X_source_group_name" } ],
-			      "FromPort": 443 } ] } ] }
-     """
-    When I run `bundle exec zaws security_group ingress_group_exists target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "true\n" 
-
-   Scenario: Declare a new vpc security group ingress group rule identified by source and target. Create it cause it doesn't exist. Also, should append the command to remove the security group to file.
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-      {	"SecurityGroups": [] }
-     """
-    And I double `aws --region us-west-1 ec2 authorize-security-group-ingress --group-id X_target_group_name --source-security-group-owner-id X_source_group_name --protocol tcp --port 443` with stdout:
-     """
-      {	"return": "true" }
-     """
-    When I run `bundle exec zaws security_group declare_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id`
-	Then the output should contain "Ingress group rule created.\n"
-
-   Scenario: Declare a new vpc security group ingress group rule identified by source and target. Do not create it because it does exist.
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-	 {	"SecurityGroups": [ { 
-	        "GroupName": "target_group_name",
-			"GroupId": "X_target_group_name",
-			"IpPermissions": [ {
-				  "ToPort": 443,
-				  "IpProtocol": "tcp",
-				  "IpRanges": [],
-				  "UserIdGroupPairs": [ {
-					 "UserId": "958601521864",
-					 "GroupId": "X_source_group_name" } ],
-			      "FromPort": 443 } ] } ] }
-     """
-    Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws security_group declare_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id --undofile undo.sh.1`
-	Then the output should contain "Ingress group rule not created. Exists already.\n"
-    And the file "undo.sh.1" should contain "zaws security_group delete_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id $XTRA_OPTS"
-
-   Scenario: Perform a nagios check, with the result indicatin OK (exit 0), indicating declaring a vpc security group ingress group requires no action because it exists.
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-	 {	"SecurityGroups": [ { 
-	        "GroupName": "target_group_name",
-			"GroupId": "X_target_group_name",
-			"IpPermissions": [ {
-				  "ToPort": 443,
-				  "IpProtocol": "tcp",
-				  "IpRanges": [],
-				  "UserIdGroupPairs": [ {
-					 "UserId": "958601521864",
-					 "GroupId": "X_source_group_name" } ],
-			      "FromPort": 443 } ] } ] }
-     """
-    When I run `bundle exec zaws security_group declare_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the output should contain "OK: Security group ingress group rule exists.\n"
-    And the exit status should be 0
-		
-   Scenario: Perform a nagios check, with the result indicatin CRITICAL (exit 2), indicating declaring a security group ingress group requires action because it does not exist.
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-      {	"SecurityGroups": [] }
-     """
-    When I run `bundle exec zaws security_group declare_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the output should contain "CRITICAL: Security group ingress group rule does not exist.\n"
-    And the exit status should be 2
-
-   Scenario: Delete a vpc security group ingress group rule, but skip it cause it does not exist
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-      {	"SecurityGroups": [] }
-     """
-    When I run `bundle exec zaws security_group delete_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security group ingress group rule does not exist. Skipping deletion.\n" 
-
-   Scenario: Delete a vpc security group ingress group rule
-    Given 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=target_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "target_group_name","GroupId": "X_target_group_name" } ] }
-     """
-	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=source_group_name'` with stdout:
-     """
-	 {	"SecurityGroups": [ { "GroupName": "source_group_name","GroupId": "X_source_group_name" } ] }
-	 """
-    And I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id' 'Name=group-id,Values=X_target_group_name' 'Name=ip-permission.group-id,Values=X_source_group_name' 'Name=ip-permission.protocol,Values=tcp' 'Name=ip-permission.to-port,Values=443'` with stdout:
-     """
-	 {	"SecurityGroups": [ { 
-	        "GroupName": "target_group_name",
-			"GroupId": "X_target_group_name",
-			"IpPermissions": [ {
-				  "ToPort": 443,
-				  "IpProtocol": "tcp",
-				  "IpRanges": [],
-				  "UserIdGroupPairs": [ {
-					 "UserId": "958601521864",
-					 "GroupId": "X_source_group_name" } ],
-			      "FromPort": 443 } ] } ] }
-     """
-    And I double `aws --region us-west-1 ec2 revoke-security-group-ingress --group-id X_target_group_name --source-security-group-owner-id X_source_group_name --protocol tcp --port 443` with stdout:
-     """
-       { "return": "true" }         
-     """
-    When I run `bundle exec zaws security_group delete_ingress_group target_group_name source_group_name tcp 443 --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security group ingress group rule deleted.\n" 
-
-

data/feature/security_group/security_group.feature

@@ -1,107 +0,0 @@
-Feature: Security Group 
-  Security Group(s) are viewable
-	 
-   Scenario: Determine a security group identified by name and vpc has NOT been created
-    Given 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": [] }
-     """
-    When I run `bundle exec zaws security_group exists_by_name my_security_group_name --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "false\n" 
-
-   Scenario: Determine a security group identified by name and vpc has been created
-    Given 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" } ] }
-     """
-    When I run `bundle exec zaws security_group exists_by_name my_security_group_name --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "true\n" 
-
-   Scenario: Determine a security group identified by name has NOT been created
-    Given I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=group-name,Values=my_security_group_name'` with stdout:
-     """
-      {	"SecurityGroups": [] }
-     """
-    When I run `bundle exec zaws security_group exists_by_name my_security_group_name --region us-west-1`
-    Then the output should contain "false\n" 
-
-   Scenario: Determine a security group identified by name has been created
-    Given I double `aws --output json --region us-west-1 ec2 describe-security-groups --filter 'Name=group-name,Values=my_security_group_name'` with stdout:
-     """
-      {	"SecurityGroups": [ { "GroupName": "my_security_group_name" } ] }
-     """
-    When I run `bundle exec zaws security_group exists_by_name my_security_group_name --region us-west-1`
-    Then the output should contain "true\n" 
-
-   Scenario: Delete a security group in a vpc, but skip it cause it does not exist
-    Given 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": [] }
-     """
-    When I run `bundle exec zaws security_group delete my_security_group_name --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security Group does not exist. Skipping deletion.\n" 
-
-   Scenario: Delete a security group in a vpc
-    Given 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-abcd1234" } ] }
-     """
-    And I double `aws --region us-west-1 ec2 delete-security-group --group-id sg-abcd1234` with stdout:
-     """
-       { "return": "true" }         
-     """
-    When I run `bundle exec zaws security_group delete my_security_group_name --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security Group deleted.\n" 
-
-   Scenario: Declare a new security group in vpc, but don't create it cause it exists
-     Given 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" } ] }
-      """
-    When I run `bundle exec zaws security_group declare my_security_group_name 'My security gorup' --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security Group Exists Already. Skipping Creation.\n"
-
-   Scenario: Declare a new security group in vpc
-    Given 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": [] }
-      """
-    And I double `aws --output json --region us-west-1 ec2 create-security-group --vpc-id my_vpc_id --group-name my_security_group_name --description 'My security group'` with stdout:
-      """
-        { "return": "true" }
-      """
-    When I run `bundle exec zaws security_group declare my_security_group_name 'My security group' --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "Security Group Created.\n"
-
-   Scenario: Perform a nagios check, with the result indicatin OK (exit 0), indicating declaring a security group requires no action because it exists.
-	Given 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" } ] }
-      """
-    When I run `bundle exec zaws security_group declare my_security_group_name 'My security gorup' --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the output should contain "OK: Security Group Exists.\n"
-    And the exit status should be 0
-		
-   Scenario: Perform a nagios check, with the result indicatin CRITICAL (exit 2), indicating declaring a security group requires action because it does not exist.
-     Given 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": [] }
-      """
-    When I run `bundle exec zaws security_group declare my_security_group_name 'My security group' --region us-west-1 --vpcid my_vpc_id --nagios`
-	Then the output should contain "CRITICAL: Security Group Does Not Exist.\n"
-    And the exit status should be 2
-
-   Scenario: Declaring a security group, should append the command to remove the security group to file.
-	Given 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": [] }
-      """
-    And I double `aws --output json --region us-west-1 ec2 create-security-group --vpc-id my_vpc_id --group-name my_security_group_name --description 'My security group'` with stdout:
-      """
-        { "return": "true" }
-      """
-	Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws security_group declare my_security_group_name 'My security group' --region us-west-1 --vpcid my_vpc_id --undofile undo.sh.1`
-	Then the output should contain "Security Group Created.\n"
-	And the file "undo.sh.1" should contain "zaws security_group delete my_security_group_name --region us-west-1 --vpcid my_vpc_id $XTRA_OPTS"
-

data/feature/security_group/view.feature

@@ -1,23 +0,0 @@
-Feature: Security Group 
-  Security Group(s) are viewable
-    
-  Scenario: Get security groups in a human readable table. 
-    Given I double `aws --output table --region us-west-1 ec2 describe-security-groups` with "AWS Security Group Table Output" 
-    When I run `bundle exec zaws security_group view --region us-west-1 --viewtype table`
-    Then the stdout should contain "AWS Security Group Table Output\n" 
-
-  Scenario: Get security groups in a human readable table form by default 
-    Given I double `aws --output table --region us-west-1 ec2 describe-security-groups` with "AWS Security Group Table Output" 
-    When I run `bundle exec zaws security_group view --region us-west-1`
-    Then the stdout should contain "AWS Security Group Table Output\n" 
-
-  Scenario: Get security groups in JSON form 
-    Given I double `aws --output json --region us-west-1 ec2 describe-security-groups` with "AWS Security Group JSON Output" 
-    When I run `bundle exec zaws security_group view --region us-west-1 --viewtype json`
-    Then the stdout should contain "AWS Security Group JSON Output\n" 
-
-  Scenario: Get security groups from specified vpcid
-    Given I double `aws --output table --region us-west-1 ec2 describe-security-groups --filter 'Name=vpc-id,Values=my_vpc_id'` with "AWS Security Group Table Output" 
-    When I run `bundle exec zaws security_group view --region us-west-1 --vpcid my_vpc_id`
-    Then the stdout should contain "AWS Security Group Table Output\n" 
-   

data/feature/subnet/subnet.feature

@@ -1,94 +0,0 @@
-Feature: Subnet
-  Subnets should be createable once in a specific availability zone.
-	 
-  Scenario: Determine a subnet has NOT been created in vpc
-    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": [] }
-     """
-    When I run `bundle exec zaws subnet exists my_cidr_block my_vpc_id --region us-west-1`
-    Then the output should contain "false\n" 
-
-  Scenario: Determine a subnet has been created in vpc
-    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" } ] }
-     """
-    When I run `bundle exec zaws subnet exists my_cidr_block my_vpc_id --region us-west-1`
-    Then the output should contain "true\n" 
-
-  Scenario: Declare a subnet but do not create it if it exists
-    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" } ] }
-     """
-    When I run `bundle exec zaws subnet declare my_cidr_block us-west-1a my_vpc_id --region us-west-1`
-    Then the output should contain "No action needed. Subnet exists already.\n" 
-    And the exit status should be 0
-
-  Scenario: Declare a subnet and create 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": [] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 create-subnet --vpc-id my_vpc_id --cidr-block my_cidr_block --availability-zone us-west-1a` with stdout:
-     """
-       { "Subnet": { "State": "available" } }        
-     """
-    When I run `bundle exec zaws subnet declare my_cidr_block us-west-1a my_vpc_id --region us-west-1`
-    Then the output should contain "Subnet created.\n"
-    And the exit status should be 0
-
-   Scenario: Delete a subnet, but skip it cause it does not exist
-    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": [] }
-     """
-    When I run `bundle exec zaws subnet delete my_cidr_block my_vpc_id --region us-west-1`
-    Then the output should contain "Subnet does not exist. Skipping deletion.\n" 
-
-   Scenario: Delete a subnet
-    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 --region us-west-1 ec2 delete-subnet --subnet-id X` with stdout:
-     """
-       { "return": "true" }         
-     """
-    When I run `bundle exec zaws subnet delete my_cidr_block my_vpc_id --region us-west-1`
-    Then the output should contain "Subnet deleted.\n" 
-
-   Scenario: Perform a nagios check, with the result indicatin OK (exit 0), indicating declaring a subnet requires no action because it exists.
-    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" } ] }
-     """
-    When I run `bundle exec zaws subnet declare my_cidr_block us-west-1a my_vpc_id --region us-west-1 --nagios`
-	Then the output should contain "OK: Subnet Exists.\n"
-    And the exit status should be 0
-		
-   Scenario: Perform a nagios check, with the result indicatin CRITICAL (exit 2), indicating declaring a subnet requires action because it does not exist.
-    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": [] }
-     """
-    When I run `bundle exec zaws subnet declare my_cidr_block us-west-1a my_vpc_id --region us-west-1 --nagios`
-	Then the output should contain "CRITICAL: Subnet Does Not Exist.\n"
-    And the exit status should be 2
-
-   Scenario: Declaring a subnet, should append the command to remove the subnet to 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": [] }
-     """
-    And I double `aws --output json --region us-west-1 ec2 create-subnet --vpc-id my_vpc_id --cidr-block my_cidr_block --availability-zone us-west-1a` with stdout:
-     """
-       { "Subnet": { "State": "available" } }        
-     """
-	Given an empty file named "undo.sh.1" 
-    When I run `bundle exec zaws subnet declare my_cidr_block us-west-1a my_vpc_id --region us-west-1 --undofile undo.sh.1`
-    Then the output should contain "Subnet created.\n" 
-	And the file "undo.sh.1" should contain "zaws subnet delete my_cidr_block my_vpc_id --region us-west-1 $XTRA_OPTS"
-
-

data/feature/subnet/view.feature

@@ -1,24 +0,0 @@
-Feature: Subnet
-  Subnets should be createable once in a specific availability zone.
-    
-  Scenario: Get subnets in json 
-    Given I double `aws --output json --region us-west-1 ec2 describe-subnets` with "< AWS Subnet Json Output >" 
-    When I run `bundle exec zaws subnet view --region us-west-1 --viewtype json`
-    Then the stdout should contain "< AWS Subnet Json Output >\n" 
-
-  Scenario: Get subnets in table form by default 
-    Given I double `aws --output table --region us-west-1 ec2 describe-subnets` with "< AWS Subnet Table Output >" 
-    When I run `bundle exec zaws subnet view --region us-west-1`
-    Then the stdout should contain "< AWS Subnet Table Output >\n" 
-
-  Scenario: Get subnets in table form when specified 
-    Given I double `aws --output table --region us-west-1 ec2 describe-subnets` with "< AWS Subnet Table Output >" 
-    When I run `bundle exec zaws subnet view --region us-west-1 --viewtype table`
-    Then the output should contain "< AWS Subnet Table Output >\n" 
-
-  Scenario: Get subnets from specified vpcid
-    Given I double `aws --output table --region us-west-1 ec2 describe-subnets --filter 'Name=vpc-id,Values=my_vpc_id'` with "< AWS Subnet Table Output >" 
-    When I run `bundle exec zaws subnet view --region us-west-1 --vpcid my_vpc_id`
-    Then the output should contain "< AWS Subnet Table Output >\n" 
-
-

data/feature/support/env.rb

@@ -1,14 +0,0 @@
-require 'coveralls'
-Coveralls.wear_merged!
-SimpleCov.merge_timeout 3600
-
-require 'aruba/cucumber'
-require 'aruba-doubles/cucumber'
-
-Before do
-  @aruba_timeout_seconds = 8
-  # This is using the aruba helper, 
-  # cf. https://github.com/cucumber/aruba/blob/master/lib/aruba/api.rb
-  set_env('COVERAGE', 'true')
-  # This could also be accomplished with the "I set the environment variables to:" step
-end