stack_master 1.3.1 → 1.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 95e15942f9d3602d9e7c5ba3f48004b285bccb30fab4bca829739582a435b6f9
-  data.tar.gz: 6982d4d3c00e00cdea0ac5237024739a2672bbe576fb3e265a0bbfc163d5308a
+  metadata.gz: 718e9ceaea1d3ec8a5ad3f5087947e8d99b0acbc9d9cf00a7b9195a6c527bd9c
+  data.tar.gz: e22b0c545568097c3f94eea29453e3020436e14ec002a3c1653d39a38028a268
 SHA512:
-  metadata.gz: cd77263d4ea01921c1b1f82c75b2f86fd066f537897628d18c71204ab26e403dda32f69366e4a45d4688769753ed0ba1514a5492137c9a1e274d9a0d1c12af9d
-  data.tar.gz: 684a1c3870be5dfd9312dd2ce85a92039aab6cdc8add0f1f788003ae9402f7ea7355f61282eb33233e518f1d79df08251c2f9479435524a6586ec51432c0cf5f
+  metadata.gz: b5d481814fbfbe8dc7e1474802c38eb0740ebe51b3112c5c5b12ec728c3e0dc0a71a41b61de2a27475f93589cafa0782f44c928889e8ecfe17a6ed5a36647eaf
+  data.tar.gz: d0f72299b00a8abf372c64247b0c5552fce38050e65db1aa6a52721859bb8d0e56b289f0f430730bad794d2b829900ecff52d5db8e3dd86f83354d3bb2e083b3

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at stackmaster@googlegroups.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org

data/README.md

@@ -4,7 +4,7 @@
 [![Gem Version](https://badge.fury.io/rb/stack_master.svg)](https://badge.fury.io/rb/stack_master)
 [![Build Status](https://travis-ci.org/envato/stack_master.svg?branch=master)](https://travis-ci.org/envato/stack_master)
 
-StackMaster is a CLI tool to manage CloudFormation stacks, with the following features:
+StackMaster is a CLI tool to manage [CloudFormation](https://aws.amazon.com/cloudformation/) stacks, with the following features:
 
 - Synchronous visibility into stack updates. See exactly what is changing and
   what will happen before agreeing to apply a change.
@@ -26,7 +26,7 @@ are displayed for review.
 
 Stack parameters can be dynamically resolved at runtime using one of the
 built in parameter resolvers. Parameters can be sourced from GPG encrypted YAML
-files, other stacks outputs, by querying various AWS API's to get resource ARNs
+files, other stacks outputs, by querying various AWS APIs to get resource ARNs,
 etc.
 
 ## Installation
@@ -103,7 +103,7 @@ stacks:
 ## S3
 
 StackMaster can optionally use S3 to store the templates before creating a stack.
-This requires to configure an S3 bucket in stack_master.yml:
+This requires you to configure an S3 bucket in stack_master.yml:
 
 ```yaml
 stack_defaults:
@@ -125,7 +125,6 @@ stacks:
 ## Directories
 
 - `templates` - CloudFormation, SparkleFormation or CfnDsl templates.
-- `polices` - Stack policies.
 - `parameters` - Parameters as YAML files.
 - `secrets` - GPG encrypted secret files.
 - `policies` - Stack policy JSON files.
@@ -133,7 +132,7 @@ stacks:
 ## Templates
 
 StackMaster supports CloudFormation templates in plain JSON or YAML. Any `.yml` or `.yaml` file will be processed as
-YAML. While any `.json` file will be processed as JSON.
+YAML, while any `.json` file will be processed as JSON.
 
 ### Ruby DSLs
 By default, any template ending with `.rb` will be processed as a [SparkleFormation](https://github.com/sparkleformation/sparkle_formation)
@@ -165,7 +164,7 @@ key_name: myapp-us-east-1
 ### Compile Time Parameters
 
 Compile time parameters can be used for [SparkleFormation](http://www.sparkleformation.io) templates. It conforms and 
-allows you to use the [Compile Time Parameters](http://www.sparkleformation.io/docs/sparkle_formation/compile-time-parameters.html) feature
+allows you to use the [Compile Time Parameters](http://www.sparkleformation.io/docs/sparkle_formation/compile-time-parameters.html) feature.
 
 A simple example looks like this
 
@@ -184,7 +183,7 @@ Keys in parameter files are automatically converted to camel case.
 Parameter values can be sourced dynamically using parameter resolvers.
 
 One benefit of using parameter resolvers instead of hard coding values like VPC
-ID's and resource ARNs is that the same configuration works cross
+IDs and resource ARNs is that the same configuration works cross
 region/account, even though the resolved values will be different.
 
 ### Stack Output
@@ -292,7 +291,7 @@ web_ami:
   latest_ami_by_tags: role=web,application=myapp
 ```
 
-Note that the corresponding array resolver is named `latest_amis_by_tags`
+Note that the corresponding array resolver is named `latest_amis_by_tags`.
 
 ### Latest AMI by attribute
 
@@ -308,7 +307,7 @@ bastion_ami:
       name: ubuntu/images/hvm/ubuntu-wily-15.10-amd64-server-*
 ```
 
-A set of possible attributes is available in the [AWS documentation](https://docs.aws.amazon.com/sdkforruby/api/Aws/EC2/Client.html#describe_images-instance_method)
+A set of possible attributes is available in the [AWS documentation](https://docs.aws.amazon.com/sdkforruby/api/Aws/EC2/Client.html#describe_images-instance_method).
 
 Any value can be an array of possible matches.
 
@@ -331,7 +330,7 @@ To create a resolver named my_resolver:
 ```
 lib/stack_master/parameter_resolvers/my_resolver.rb
 ```
-  * That file need to contain a class named `StackMaster::ParameterResolvers::MyResolver`
+  * That file needs to contain a class named `StackMaster::ParameterResolvers::MyResolver`
     that implements a `resolve` method and an initializer taking 2 parameters :
 ```ruby
 module StackMaster
@@ -503,7 +502,7 @@ stack_master apply [region-or-alias] # Create or update stacks in the given regi
 stack_master apply # Create or update all stacks
 stack_master --changed apply # Create or update all stacks that have changed
 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 diff [region-or-alias] [stack-name] # Display a stack template 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

data/lib/stack_master.rb

@@ -1,8 +1,15 @@
-require "commander"
-require "yaml"
-require "aws-sdk"
+require 'commander'
+require 'yaml'
+require "aws-sdk-cloudformation"
+require "aws-sdk-ec2"
+require "aws-sdk-s3"
+require "aws-sdk-sns"
+require "aws-sdk-ssm"
 require "colorize"
 require 'active_support/core_ext/string'
+require 'multi_json'
+
+MultiJson.use :json_gem
 
 module StackMaster
   extend self

data/lib/stack_master/test_driver/cloud_formation.rb

@@ -1,3 +1,5 @@
+require 'securerandom'
+
 module StackMaster
   module TestDriver
     class Stack

data/lib/stack_master/version.rb

@@ -1,3 +1,3 @@
 module StackMaster
-  VERSION = "1.3.1"
+  VERSION = "1.4.0"
 end

data/stack_master.gemspec

@@ -28,7 +28,11 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency "timecop"
   spec.add_dependency "ruby-progressbar"
   spec.add_dependency "commander"
-  spec.add_dependency "aws-sdk", "~> 2.6"
+  spec.add_dependency "aws-sdk-cloudformation", "~> 1"
+  spec.add_dependency "aws-sdk-ec2", "~> 1"
+  spec.add_dependency "aws-sdk-s3", "~> 1"
+  spec.add_dependency "aws-sdk-sns", "~> 1"
+  spec.add_dependency "aws-sdk-ssm", "~> 1"
   spec.add_dependency "diffy"
   spec.add_dependency "erubis"
   spec.add_dependency "colorize"
@@ -38,4 +42,5 @@ Gem::Specification.new do |spec|
   spec.add_dependency "dotgpg"
   spec.add_dependency "deep_merge"
   spec.add_dependency "cfndsl"
+  spec.add_dependency "multi_json"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: stack_master
 version: !ruby/object:Gem::Version
-  version: 1.3.1
+  version: 1.4.0
 platform: ruby
 authors:
 - Steve Hodgkiss
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-03-18 00:00:00.000000000 Z
+date: 2018-04-19 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -138,19 +138,75 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: aws-sdk
+  name: aws-sdk-cloudformation
   requirement: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.6'
+        version: '1'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '2.6'
+        version: '1'
+- !ruby/object:Gem::Dependency
+  name: aws-sdk-ec2
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+- !ruby/object:Gem::Dependency
+  name: aws-sdk-s3
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+- !ruby/object:Gem::Dependency
+  name: aws-sdk-sns
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+- !ruby/object:Gem::Dependency
+  name: aws-sdk-ssm
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - "~>"
+      - !ruby/object:Gem::Version
+        version: '1'
 - !ruby/object:Gem::Dependency
   name: diffy
   requirement: !ruby/object:Gem::Requirement
@@ -277,6 +333,20 @@ dependencies:
     - - ">="
       - !ruby/object:Gem::Version
         version: '0'
+- !ruby/object:Gem::Dependency
+  name: multi_json
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 description: ''
 email:
 - steve@hodgkiss.me
@@ -289,6 +359,7 @@ files:
 - ".gitignore"
 - ".rspec"
 - ".travis.yml"
+- CODE_OF_CONDUCT.md
 - Gemfile
 - LICENSE.txt
 - README.md