stack_master 0.0.4 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 47ceb9c3a194f4352336f7994f8c4034c8d0ff6e
-  data.tar.gz: a990f7e54348aee9b55378ea9518c1518ae4d4eb
+  metadata.gz: 26523ee5aa16ba21756d486d7619b09c2fa2ee77
+  data.tar.gz: 56830d0b945a777db396799c98066742d2c1e4bd
 SHA512:
-  metadata.gz: 8dafc6386c511101ab2da220d0c632b823fc2add8f6d88430d0cf11f6c94c8256c7b99bc1661f5db3e62051e0383952b3f769baa31dfcae8919305db4390a27e
-  data.tar.gz: fa452352356d15ba2fc08ab728e6709a72f793250bd325fa990cc8cb9ccfa15a7ec1b75ea5c5af65deedf3b0dd7f952691f0b5797f1d10c042faa83b48121304
+  metadata.gz: eff6fcc6ca243f1149db52968c0effc3e963cb161ed4a88863fc420932bd3c3297c895d964fe3acd1a0d0c036ba64ece99f2c8d6093e4d9dc24f951276d9d427
+  data.tar.gz: 9623fa5996449668f58d9c1f34b3774b5469d6332ba56c011773264654b0e8e91e50a9590ef02c0a1030f90b8b29db025096fa515dd358f33a95d4e445415289

data/README.md

@@ -151,6 +151,16 @@ ssh_sg:
   security_group: SSHSecurityGroup
 ```
 
+### Security Groups
+
+An array of security group names can also be provided.
+```yaml
+ssh_sg:
+  security_groups:
+    - SSHSecurityGroup
+    - WebAccessSecurityGroup
+```
+
 ### SNS Topic
 
 Looks up an SNS topic by name and returns the ARN.
@@ -169,6 +179,8 @@ web_ami:
   latest_ami_by_tags: role=web,application=myapp
 ```
 
+Note that the corresponding array resolver is named `latest_amis_by_tags`
+
 ### Custom parameter resolvers
 
 New parameter resolvers can be created in a separate gem.
@@ -184,7 +196,9 @@ lib/stack_master/parameter_resolvers/my_resolver.rb
 ```ruby
 module StackMaster
   module ParameterResolvers
-    class MyResolver
+    class MyResolver < Resolver
+      array_resolver # Also create a MyResolvers resolver to handle arrays
+
       def initialize(config, stack_definition)
         @config = config
         @stack_definition = stack_definition
@@ -204,18 +218,49 @@ vpc_id:
   my_resolver: dummy_value
 ```
 
+## Resolver Arrays
+
+Most resolvers support taking an array of values that will each be resolved.
+Unless stated otherwise in the documentation, the array version of the
+resolver will be named with the [pluralized](http://api.rubyonrails.org/classes/ActiveSupport/Inflector.html#method-i-pluralize) 
+name of the original resolver.
+
+When creating a new resolver, one can automatically create the array resolver by adding a `array_resolver` statement
+in the class definition, with an optional class name if different from the default one.
+```
+module StackMaster
+  module ParameterResolvers
+    class MyResolver < Resolver
+      array_resolver class_name: 'MyCustomArrayResolver'
+      ...
+    end
+  end
+end
+```
+In that example, using the array resolver would look like:
+```
+my_parameter:
+  my_custom_array_resolver:
+    - value1
+    - value2
+```
+
 ## Commands
 
 ```bash
 stack_master help # Display up to date docs on the commands available
 stack_master init # Initialises a directory structure and stack_master.yml file
 stack_master list # Lists stack definitions
-stack_master apply <region-or-alias> <stack-name> # Create or update a stack
-stack_master diff <region-or-alias> <stack-name> # Display a stack tempalte and parameter diff
-stack_master delete <region-or-alias> <stack-name> # Delete a stack
-stack_master events <region-or-alias> <stack-name> # Display events for a stack
-stack_master outputs <region-or-alias> <stack-name> # Display outputs for a stack
-stack_master resources <region-or-alias> <stack-name> # Display outputs for a stack
+stack_master apply [region-or-alias] [stack-name] # Create or update a stack
+stack_master apply [region-or-alias] [stack-name] [region-or-alias] [stack-name] # Create or update multiple stacks
+stack_master apply [region-or-alias] # Create or update stacks in the given region
+stack_master apply # Create or update all stacks
+stack_master --yes apply [region-or-alias] [stack-name] # Create or update a stack non-interactively (forcing yes)
+stack_master diff [region-or-alias] [stack-name] # Display a stack tempalte and parameter diff
+stack_master delete [region-or-alias] [stack-name] # Delete a stack
+stack_master events [region-or-alias] [stack-name] # Display events for a stack
+stack_master outputs [region-or-alias] [stack-name] # Display outputs for a stack
+stack_master resources [region-or-alias] [stack-name] # Display outputs for a stack
 stack_master status # Displays the status of each stack
 ```
 

data/Rakefile

@@ -23,3 +23,5 @@ begin
   end
 rescue LoadError
 end
+
+task :default => [:features, :spec]

data/bin/stack_master

@@ -10,7 +10,8 @@ end
 trap("SIGINT") { raise StackMaster::CtrlC }
 
 begin
-  StackMaster::CLI.new(ARGV.dup).execute!
+  result = StackMaster::CLI.new(ARGV.dup).execute!
+  exit !!result
 rescue StackMaster::CtrlC
   StackMaster.stdout.puts "Exiting..."
 end

data/features/apply.feature

@@ -62,19 +62,13 @@ Feature: Apply command
         end
       end
       """
-    And I set the environment variables to:
-      | variable | value |
-      | STUB_AWS | true  |
 
   Scenario: Run apply and create a new stack
-    Given I set the environment variables to:
-      | variable | value |
-      | ANSWER   | y     |
-    And I stub the following stack events:
+    Given 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 apply us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master apply us-east-1 myapp-vpc --trace`
     And the output should contain all of these lines:
       | Stack diff:                                                                    |
       | +    "Vpc": {                                                                  |
@@ -84,10 +78,8 @@ Feature: Apply command
     Then the exit status should be 0
 
   Scenario: Run apply and don't create the stack
-    Given I set the environment variables to:
-      | variable | value |
-      | ANSWER   | n     |
-    When I run `stack_master apply us-east-1 myapp-vpc --trace` interactively
+    Given I will answer prompts with "n"
+    When I run `stack_master apply us-east-1 myapp-vpc --trace`
     And the output should contain all of these lines:
       | Stack diff:      |
       | +    "Vpc": {    |
@@ -97,11 +89,62 @@ Feature: Apply command
     And the output should not match /2020-10-29 00:00:00 \+[0-9]{4} myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE/ 
     Then the exit status should be 0
 
+  Scenario: Run apply with region only and create 2 stacks
+    Given 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 |
+      | 1        | 1        | myapp-web  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-web  | myapp-web           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    When I run `stack_master apply us-east-1 --trace`
+    And the output should contain all of these lines:
+      | Stack diff:                                                                    |
+      | +    "Vpc": {                                                                  |
+      | Parameters diff:                                                               |
+      | KeyName: my-key                                                                |
+
+  Scenario: Run apply nothing and create 2 stacks
+    Given 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 |
+      | 1        | 1        | myapp-web  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-web  | myapp-web           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    When I run `stack_master apply --trace`
+    And the output should contain all of these lines:
+      | Stack diff:                                                                    |
+      | +    "Vpc": {                                                                  |
+      | Parameters diff:                                                               |
+      | KeyName: my-key                                                                |
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE/
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-web AWS::CloudFormation::Stack CREATE_COMPLETE/
+    Then the exit status should be 0
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE/
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-web AWS::CloudFormation::Stack CREATE_COMPLETE/
+    Then the exit status should be 0
+
+  Scenario: Run apply with 2 specific stacks and create 2 stacks
+    Given 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 |
+      | 1        | 1        | myapp-web  | TestSg              | CREATE_COMPLETE | AWS::EC2::SecurityGroup    | 2020-10-29 00:00:00 |
+      | 1        | 1        | myapp-web  | myapp-web           | CREATE_COMPLETE | AWS::CloudFormation::Stack | 2020-10-29 00:00:00 |
+    When I run `stack_master apply us-east-1 myapp-vpc us-east-1 myapp-web --trace`
+    And the output should contain all of these lines:
+      | Stack diff:                                                                    |
+      | +    "Vpc": {                                                                  |
+      | Parameters diff:                                                               |
+      | KeyName: my-key                                                                |
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE/
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-web AWS::CloudFormation::Stack CREATE_COMPLETE/
+    Then the exit status should be 0
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-vpc AWS::CloudFormation::Stack CREATE_COMPLETE/
+    And the output should match /2020-10-29 00:00:00 \+[0-9]{4} myapp-web AWS::CloudFormation::Stack CREATE_COMPLETE/
+    Then the exit status should be 0
+
   Scenario: Run apply on an existing stack
-    Given I set the environment variables to:
-      | variable | value |
-      | ANSWER   | y     |
-    And I stub the following stack events:
+    Given 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 |
@@ -141,7 +184,7 @@ Feature: Apply command
         }
       }
       """
-    When I run `stack_master apply us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master apply us-east-1 myapp-vpc --trace`
     And the output should contain all of these lines:
       | Stack diff:                                                                    |
       | -    "TestSg2": {                                                              |
@@ -149,10 +192,7 @@ Feature: Apply command
     Then the exit status should be 0
 
   Scenario: Create a stack using a stack output resolver
-    Given I set the environment variables to:
-      | variable | value |
-      | ANSWER   | y     |
-    And a file named "parameters/myapp_web.yml" with:
+    Given a file named "parameters/myapp_web.yml" with:
       """
       VpcId:
         stack_output: myapp-vpc/VpcId
@@ -164,7 +204,7 @@ Feature: Apply command
     And I stub the following stacks:
       | stack_id | stack_name | region    | outputs          |
       | 1        | myapp-vpc  | us-east-1 | VpcId=vpc-xxxxxx |
-    When I run `stack_master apply us-east-1 myapp-web --trace` interactively
+    When I run `stack_master apply us-east-1 myapp-web --trace`
     And the output should contain all of these lines:
       | Stack diff:                                                                    |
       | +    "TestSg": {                                                               |
@@ -188,9 +228,6 @@ Feature: Apply command
       """
       {}
       """
-    And I set the environment variables to:
-      | variable | value |
-      | ANSWER   | y     |
     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 |
@@ -231,7 +268,7 @@ Feature: Apply command
         }
       }
       """
-    When I run `stack_master apply us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master apply us-east-1 myapp-vpc --trace`
     Then the stack "myapp-vpc" should have a policy with the following:
       """
       {}

data/features/delete.feature

@@ -1,41 +1,28 @@
 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:
+    Given 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
+    When I run `stack_master delete us-east-1 myapp-vpc --trace`
     And the output should match /2020-10-29 00:00:00 \+[0-9]{4} 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
+    When I run `stack_master delete us-east-1 myapp-vpc --trace`
     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     |
+    Given I will answer prompts with "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
+    When I run `stack_master delete us-east-1 myapp-vpc --trace`
     And the output should contain all of these lines:
       | Stack update aborted |
     Then the exit status should be 0

data/features/diff.feature

@@ -47,15 +47,9 @@ Feature: Diff command
         }
       }
       """
-    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:
+    Given 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":
@@ -91,17 +85,14 @@ Feature: Diff command
         }
       }
       """
-    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master diff us-east-1 myapp-vpc --trace`
     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:
+    Given 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":
@@ -137,17 +128,14 @@ Feature: Diff command
         }
       }
       """
-    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master diff us-east-1 myapp-vpc --trace`
     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:
+    Given 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":
@@ -183,7 +171,7 @@ Feature: Diff command
         }
       }
       """
-    When I run `stack_master diff us-east-1 myapp-vpc --trace` interactively
+    When I run `stack_master diff us-east-1 myapp-vpc --trace`
     And the output should contain all of these lines:
     | -        "GroupDescription": "Changed description" |
     | +        "GroupDescription": "Test SG 2",          |

data/features/events.feature

@@ -23,13 +23,9 @@ Feature: Events command
         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:
+    Given 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 |

data/features/outputs.feature

@@ -22,13 +22,9 @@ Feature: Outputs command
         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:
+    Given 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":

data/features/region_aliases.feature

@@ -50,10 +50,6 @@ Feature: Region aliases
       | 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`

data/features/resources.feature

@@ -22,12 +22,9 @@ Feature: Resources command
         end
       end
       """
-    And I set the environment variables to:
-      | variable | value |
-      | STUB_AWS | true  |
 
   Scenario: Show resources
-    And I stub the following stacks:
+    Given 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:

data/features/stack_defaults.feature

@@ -71,15 +71,9 @@ Feature: Stack defaults
       | 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
+    When I run `stack_master apply ap-southeast-2 myapp-vpc --trace`
     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: