stack_master 0.0.1

data/features/delete.feature

@@ -0,0 +1,43 @@
+Feature: Delete command
+
+  Background:
+    Given I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+
+  Scenario: Run a delete command on a stack that exists
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+     And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 |
+    And I stub the following stack events:
+      | stack_id | event_id | stack_name | logical_resource_id | resource_status | resource_type              | timestamp           |
+      |        1 |        1 | myapp-vpc  | myapp-vpc           | DELETE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    When I run `stack_master delete us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+    | 2020-10-29 00:00:00 +1100 myapp-vpc AWS::CloudFormation::Stack DELETE_COMPLETE |
+    Then the exit status should be 0
+
+  Scenario: Run a delete command on a stack that does not exists
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+    When I run `stack_master delete us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+      | Stack does not exist |
+    Then the exit status should be 0
+
+  Scenario: Answer no when asked to delete stack
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | n     |
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 | 
+    When I run `stack_master delete us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+      | Stack update aborted |
+    Then the exit status should be 0
+

data/features/diff.feature

@@ -0,0 +1,191 @@
+Feature: Diff command
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      stacks:
+        us_east_1:
+          myapp_vpc:
+            template: myapp_vpc.json
+      """
+    And a directory named "parameters"
+    And a file named "parameters/myapp_vpc.yml" with:
+      """
+      KeyName: my-key
+      """
+    And a directory named "templates"
+    And a file named "templates/myapp_vpc.json" with:
+      """
+      {
+        "Description": "Test template",
+        "AWSTemplateFormatVersion": "2010-09-09",
+        "Parameters": {
+          "KeyName": {
+            "Description": "Key Name",
+            "Type": "String"
+          }
+        },
+        "Resources": {
+          "TestSg": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          },
+          "TestSg2": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG 2",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          }
+        }
+      }
+      """
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+
+  Scenario: Run diff on a stack with no changes
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters          | region    |
+      |        1 | myapp-vpc  | KeyName=changed-key | us-east-1 |
+    And I stub a template for the stack "myapp-vpc":
+      """
+      {
+        "Description": "Test template",
+        "AWSTemplateFormatVersion": "2010-09-09",
+        "Parameters": {
+          "KeyName": {
+            "Description": "Key Name",
+            "Type": "String"
+          }
+        },
+        "Resources": {
+          "TestSg": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          },
+          "TestSg2": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG 2",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          }
+        }
+      }
+      """
+    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+      | -KeyName: changed |
+      | +KeyName: my-key  |
+    Then the exit status should be 0
+
+  Scenario: Run diff on a stack with parameter changes
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 |
+    And I stub a template for the stack "myapp-vpc":
+      """
+      {
+        "Description": "Test template",
+        "AWSTemplateFormatVersion": "2010-09-09",
+        "Parameters": {
+          "KeyName": {
+            "Description": "Key Name",
+            "Type": "String"
+          }
+        },
+        "Resources": {
+          "TestSg": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          },
+          "TestSg2": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG 2",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          }
+        }
+      }
+      """
+    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+      | Stack diff: No changes      |
+      | Parameters diff: No changes |
+    Then the exit status should be 0
+
+  Scenario: Run diff on a stack with template changes
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 |
+    And I stub a template for the stack "myapp-vpc":
+      """
+      {
+        "Description": "Test template",
+        "AWSTemplateFormatVersion": "2010-09-09",
+        "Parameters": {
+          "KeyName": {
+            "Description": "Key Name",
+            "Type": "String"
+          }
+        },
+        "Resources": {
+          "TestSg": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Test SG",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          },
+          "TestSg2": {
+            "Type": "AWS::EC2::SecurityGroup",
+            "Properties": {
+              "GroupDescription": "Changed description",
+              "VpcId": {
+                "Ref": "VpcId"
+              }
+            }
+          }
+        }
+      }
+      """
+    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    And the output should contain all of these lines:
+    | -        "GroupDescription": "Changed description" |
+    | +        "GroupDescription": "Test SG 2",          |
+    Then the exit status should be 0
+

data/features/events.feature

@@ -0,0 +1,38 @@
+Feature: Events command
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      stacks:
+        us_east_1:
+          myapp_vpc:
+            template: myapp_vpc.rb
+      """
+    And a directory named "templates"
+    And a file named "templates/myapp_vpc.rb" with:
+      """
+      SparkleFormation.new(:myapp_vpc) do
+        description "Test template"
+        set!('AWSTemplateFormatVersion', '2010-09-09')
+
+        resources.vpc do
+          type 'AWS::EC2::VPC'
+          properties do
+            cidr_block '10.200.0.0/16'
+          end
+        end
+      end
+      """
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+      | ANSWER   | y     |
+
+  Scenario: View events
+    And I stub the following stack events:
+      | stack_id | event_id | stack_name | logical_resource_id | resource_status | resource_type              | timestamp           |
+      | 1        | 1        | myapp-vpc  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-vpc  | myapp-vpc           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    When I run `stack_master events us-east-1 myapp-vpc --trace`
+    And the output should contain all of these lines:
+      | 2020-10-29 00:00:00 +1100 myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE |

data/features/init.feature

@@ -0,0 +1,6 @@
+Feature: init project
+
+  Scenario: Run init
+    When I run `stack_master init us-east-1 my-app`
+    # TODO flesh this out
+    Then the exit status should be 0

data/features/outputs.feature

@@ -0,0 +1,49 @@
+Feature: Outputs command
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      stacks:
+        us_east_1:
+          myapp_vpc:
+            template: myapp_vpc.rb
+      """
+    And a directory named "templates"
+    And a file named "templates/myapp_vpc.rb" with:
+      """
+      SparkleFormation.new(:myapp_vpc) do
+        description "Test template"
+        set!('AWSTemplateFormatVersion', '2010-09-09')
+        resources.vpc do
+          type 'AWS::EC2::VPC'
+          properties do
+            cidr_block '10.200.0.0/16'
+          end
+        end
+      end
+      """
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+      | ANSWER   | y     |
+
+  Scenario: Output stack resources
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    | outputs          |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 | VpcId=vpc-123456 |
+    And I stub a template for the stack "myapp-vpc":
+      """
+      {
+      }
+      """
+    When I run `stack_master outputs us-east-1 myapp-vpc --trace`
+    And the output should contain all of these lines:
+      | VpcId      |
+      | vpc-123456 |
+
+  Scenario: Fails when the stack doesn't exist
+    When I run `stack_master outputs us-east-1 myapp-vpc --trace`
+    And the output should not contain all of these lines:
+      | VpcId      |
+      | vpc-123456 |
+    And the output should contain "Stack doesn't exist"

data/features/region_aliases.feature

@@ -0,0 +1,66 @@
+Feature: Region aliases
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      region_aliases:
+        staging: ap-southeast-2
+        production: us_east_1
+      stacks:
+        staging:
+          myapp_vpc:
+            template: myapp_vpc.rb
+        production:
+          myapp_vpc:
+            template: myapp_vpc.rb
+      """
+    And a directory named "templates"
+    And a directory named "parameters"
+    And a file named "templates/myapp_vpc.rb" with:
+      """
+      SparkleFormation.new(:myapp_vpc) do
+        description "Test template"
+        set!('AWSTemplateFormatVersion', '2010-09-09')
+
+        parameters.key_name do
+          description 'Key name'
+          type 'String'
+        end
+
+        resources.vpc do
+          type 'AWS::EC2::VPC'
+          properties do
+            cidr_block '10.200.0.0/16'
+          end
+        end
+
+        outputs do
+          vpc_id do
+            description 'A VPC ID'
+            value ref!(:vpc)
+          end
+        end
+      end
+      """
+    And a file named "parameters/myapp_vpc.yml" with:
+      """
+      key_name: my-key
+      """
+    And I stub the following stack events:
+      | stack_id | event_id | stack_name | logical_resource_id | resource_status | resource_type              | timestamp           |
+      | 1        | 1        | myapp-vpc  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-vpc  | myapp-vpc           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+      | ANSWER   | y     |
+
+  Scenario: Create a stack using region aliases
+    When I run `stack_master apply staging myapp-vpc --trace`
+    And the output should contain all of these lines:
+      | Stack diff:                                                                    |
+      | +    "Vpc": {                                                                  |
+      | Parameters diff:                                                               |
+      | KeyName: my-key                                                                |
+      | 2020-10-29 00:00:00 +1100 myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE |
+    Then the exit status should be 0

data/features/resources.feature

@@ -0,0 +1,45 @@
+Feature: Resources command
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      stacks:
+        us_east_1:
+          myapp_vpc:
+            template: myapp_vpc.rb
+      """
+    And a directory named "templates"
+    And a file named "templates/myapp_vpc.rb" with:
+      """
+      SparkleFormation.new(:myapp_vpc) do
+        description "Test template"
+        set!('AWSTemplateFormatVersion', '2010-09-09')
+        resources.vpc do
+          type 'AWS::EC2::VPC'
+          properties do
+            cidr_block '10.200.0.0/16'
+          end
+        end
+      end
+      """
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+
+  Scenario: Show resources
+    And I stub the following stacks:
+      | stack_id | stack_name | parameters       | region    |
+      | 1        | myapp-vpc  | KeyName=my-key   | us-east-1 |
+    And I stub the following stack resources:
+      | stack_name | logical_resource_id  | resource_type | timestamp           | resource_status |
+      | myapp-vpc  | Vpc                  | AWS::EC2::Vpc | 2015-11-02 06:41:58 | CREATE_COMPLETE |
+    When I run `stack_master resources us-east-1 myapp-vpc --trace`
+    And the output should contain all of these lines:
+      | Vpc                 |
+      | AWS::EC2::Vpc       |
+      | 2015-11-02 06:41:58 |
+      | CREATE_COMPLETE     |
+
+  Scenario: Fails when the stack doesn't exist
+    When I run `stack_master resources us-east-1 myapp-vpc --trace`
+    And the output should contain "Stack doesn't exist"

data/features/stack_defaults.feature

@@ -0,0 +1,88 @@
+Feature: Stack defaults
+
+  Background:
+    Given a file named "stack_master.yml" with:
+      """
+      stack_defaults:
+        tags:
+          application: my-awesome-blog
+      region_defaults:
+        ap_southeast_2:
+          notification_arns:
+          - test_arn_1
+          secret_file: staging.yml.gpg
+          tags:
+            environment: staging
+          stack_policy_file: my_policy.json
+        us_east_1:
+          notification_arns:
+          - test_arn_2
+          secret_file: production.yml.gpg
+          tags:
+            environment: production
+      stacks:
+        ap_southeast_2:
+          myapp_vpc:
+            template: myapp_vpc.rb
+            tags:
+              role: network
+            notification_arns:
+              - test_arn_3
+        us_east_1:
+          myapp_vpc:
+            template: myapp_vpc.rb
+            tags:
+              role: network
+      """
+    And a directory named "templates"
+    And a directory named "policies"
+    And a file named "templates/myapp_vpc.rb" with:
+      """
+      SparkleFormation.new(:myapp_vpc) do
+        description "Test template"
+        set!('AWSTemplateFormatVersion', '2010-09-09')
+
+        parameters.key_name do
+          description 'Key name'
+          type 'String'
+          default 'blah'
+        end
+
+        resources.vpc do
+          type 'AWS::EC2::VPC'
+          properties do
+            cidr_block '10.200.0.0/16'
+          end
+        end
+
+        outputs do
+          vpc_id do
+            description 'A VPC ID'
+            value ref!(:vpc)
+          end
+        end
+      end
+      """
+    And a file named "policies/my_policy.json" with:
+      """
+      {my: 'policy'}
+      """
+    And I stub the following stack events:
+      | stack_id | event_id | stack_name | logical_resource_id | resource_status | resource_type              | timestamp           |
+      | 1        | 1        | myapp-vpc  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-vpc  | myapp-vpc           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    And I set the environment variables to:
+      | variable | value |
+      | STUB_AWS | true  |
+    Given I set the environment variables to:
+      | variable | value |
+      | ANSWER   | y     |
+
+  Scenario: Create a stack with inherited attributes
+    When I run `stack_master apply ap-southeast-2 myapp-vpc --trace` interactively
+    Then the stack "myapp-vpc" should contain this notification ARN "test_arn_1"
+    Then the stack "myapp-vpc" should contain this notification ARN "test_arn_3"
+    And the stack "myapp-vpc" should have a policy with the following:
+      """
+      {my: 'policy'}
+      """