cloudformation_rspec 0.0.9 → 0.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
-SHA256:
-  metadata.gz: 9e741127a74f674f19e97e2d5c25dedfb96cab8eb471fe65a4ba8ba5d5e18fd4
-  data.tar.gz: 84004c6abe9054bdd0eccaf8a81996916976c29b45794fb591ef5ba098ffdbe2
+SHA1:
+  metadata.gz: 3db66fc637f051d0215b0a032ec4c4b8c53a79b8
+  data.tar.gz: 9c8369901d78964f71cab1d6663395162883d9ce
 SHA512:
-  metadata.gz: 7b0df6dabb6d58df4bc7bbbdfc70d9ced98dea284522ffc30eabf5fe31f8e15a0f39ba42ed18b293f1944af44a385e5b056370b367f5c4181c5f669b1f79e7a7
-  data.tar.gz: 98b37a583ed876cbd4fcf60ede9f642e7202010ea61ff23936ca319791bacefb70efb6000647d2c4ea2309e0158c3cfd4d0d3bc34365ab9ef7ca7ceba6633d61
+  metadata.gz: 6345dfdd804ccfa4624e262671e329a88ef21a99db8e35ede647c69477f56e7ddfa5339c3ef9003edcb11d83951077f5c2f95e9c2de55ba255b62165da12ec53
+  data.tar.gz: a97a4ddd76b905580867fdbdd2c54d48b5560a83bd06f3d6ce2e06ab9e54eac0dacf318eef66e67a687ac7659aaf57b4de6bed494dab05ae4ceb0bffaa0cc842

data/.travis.yml

@@ -0,0 +1,6 @@
+language: ruby
+rvm:
+ - 2.3.7
+ - 2.4.4
+ - 2.5.1
+script: bundle exec rake spec

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# 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, sex characteristics, 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 patrick.robinson@envato.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
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

data/LICENSE.md

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2018 Envato
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/README.md

@@ -11,12 +11,12 @@ CloudFormation RSpec enables us to use RSpec matchers test your templates agains
 ```ruby
 describe 'vpc_template' do
   let(:template_json) { File.read('fixtures/vpc.json') }
-  let(:stack) {
+  let(:stack) {{
     template_body: template_json,
     parameters: {
       "VpcCidr" => cidr,
     }
-  }
+  }}
 
   it 'is valid' do
     expect(template_json).to be_valid
@@ -75,6 +75,25 @@ describe 'vpc_template' do
 end
 ```
 
+## Development Status
+
+In production use
+
+## Maintainers
+
+Patrick Robinson (@patrobinson)
+
 ## Limitations
 
 Currently we don't support templates larger than 51,200 bytes, as this requires uploading the template to S3 first.
+
+## Contributing
+
+For bug fixes, documentation changes, and small features:  
+1. Fork it ( https://github.com/envato/cloudformation_rspec/fork )  
+2. Create your feature branch (`git checkout -b my-new-feature`)  
+3. Commit your changes (`git commit -am 'Add some feature'`)  
+4. Push to the branch (`git push origin my-new-feature`)  
+5. Create a new Pull Request  
+
+For larger new features: Do everything as above, but first also make contact with the project maintainers to be sure your change fits with the project direction and you won't be wasting effort going in the wrong direction

data/Rakefile

@@ -1,3 +1,4 @@
+require "bundler/gem_tasks"
 require 'rspec/core/rake_task'
 
 RSpec::Core::RakeTask.new

data/cloudformation-rspec.gemspec

@@ -2,7 +2,7 @@ $:.unshift File.expand_path("../lib", __FILE__)
 
 Gem::Specification.new do |gem|
   gem.name    = "cloudformation_rspec"
-  gem.version = "0.0.9"
+  gem.version = "0.1.0"
 
   gem.authors     = ["Patrick Robinson"]
   gem.email       = ["patrick.robinson@envato.com"]

data/lib/cloudformation_rspec/change_set.rb

@@ -15,7 +15,7 @@ class CloudFormationRSpec::ChangeSet
 
   @change_set_cache = {}
 
-  attr_reader :changes, :status
+  attr_reader :changes, :status, :status_reason
 
   def initialize(template_body:, parameters: {})
     @template_body = template_body
@@ -38,6 +38,7 @@ class CloudFormationRSpec::ChangeSet
     if change_set = self.class.get_from_cache(change_set_hash)
       @status = change_set.status
       @changes = change_set.changes.map { |change| CloudFormationRSpec::ResourceChange.new(change.resource_change.resource_type, change.resource_change.logical_resource_id) }
+      @status_reason = change_set.status_reason
       return change_set
     end
 
@@ -58,6 +59,7 @@ class CloudFormationRSpec::ChangeSet
     end
     @status = response.status
     @changes = response.changes.map { |change| CloudFormationRSpec::ResourceChange.new(change.resource_change.resource_type, change.resource_change.logical_resource_id) }
+    @status_reason = response.status_reason
     client.delete_change_set(change_set_name: change_set_name, stack_name: change_set_name)
     client.delete_stack(stack_name: change_set_name) if stack_created
     self.class.add_to_cache(change_set_hash, response)

data/spec/change_set_spec.rb

@@ -22,6 +22,7 @@ describe CloudFormationRSpec::ChangeSet do
     allow(cf_stub).to receive(:describe_stacks).and_return(stacks_mock)
     allow(cf_stub).to receive(:wait_until).and_return(true)
     allow(change_set_mock).to receive(:status).and_return("CREATE_COMPLETE")
+    allow(change_set_mock).to receive(:status_reason).and_return("Success")
     allow(change_set_mock).to receive(:changes).and_return([aws_change_mock])
     allow(aws_change_mock).to receive(:resource_change).and_return(aws_resource_change_mock)
     allow(stacks_mock).to receive(:stacks).and_return([stack_mock])
@@ -131,6 +132,7 @@ describe CloudFormationRSpec::ChangeSet do
     before do
       allow(cf_stub).to receive(:wait_until).and_raise(Aws::Waiters::Errors::WaiterFailed)
       allow(change_set_mock).to receive(:status).and_return("FAILED")
+      allow(change_set_mock).to receive(:status_reason).and_return("FAILED")
     end
 
     it 'just deletes the change set' do

data/spec/matchers/change_set_spec.rb

@@ -51,6 +51,7 @@ describe 'contain_in_change_set' do
     it 'fails when there is no matching resource type' do
       expect(stack).not_to contain_in_change_set("AWS::EC2::Foo", "vpc")
     end
+
   end
 
   context 'an invalid sparkleformation template' do
@@ -69,6 +70,17 @@ describe 'contain_in_change_set' do
       expect { expect(stack).not_to contain_in_change_set("AWS::EC2::Foo", "vpc") }.to raise_error(CloudFormationRSpec::Sparkle::InvalidSparkleTemplate)
     end
   end
+
+  context 'a stack that fails to generate a change set' do
+    before do
+      allow(change_set_mock).to receive(:status).and_return("FAILED")
+      allow(change_set_mock).to receive(:status_reason).and_return("failed")
+    end
+
+    it 'fails' do
+     expect(stack).not_to contain_in_change_set("AWS::EC2::VPC", "Foo")
+    end
+  end
 end
 
 describe 'have_change_set_failed' do

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: cloudformation_rspec
 version: !ruby/object:Gem::Version
-  version: 0.0.9
+  version: 0.1.0
 platform: ruby
 authors:
 - Patrick Robinson
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-08-14 00:00:00.000000000 Z
+date: 2019-06-07 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rspec
@@ -73,7 +73,10 @@ executables: []
 extensions: []
 extra_rdoc_files: []
 files:
+- ".travis.yml"
+- CODE_OF_CONDUCT.md
 - Gemfile
+- LICENSE.md
 - README.md
 - Rakefile
 - cloudformation-rspec.gemspec
@@ -115,7 +118,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.7.6
+rubygems_version: 2.6.11
 signing_key: 
 specification_version: 4
 summary: Test your CloudFormation templates