knife-ec2 0.12.0 → 0.13.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: df82616670ab17b61699fa1d344500f0c80309fa
-  data.tar.gz: e4969b3ddaac2b8173b3bc74c6b94e1916058317
+  metadata.gz: cdaebe8b7719446fee4ccf08e113714a64097e57
+  data.tar.gz: 7dcf7fdc5ac57a4ce35baba78abeb67941d1c5bb
 SHA512:
-  metadata.gz: d600ff181661d04c4702789a7042bbea70bd3c4998f4f4031e089d215c7d51e2a3499f375c1b7f3fb9a14f1186a5343b50b94fe53816b5448469c674bd252b0c
-  data.tar.gz: b46b7174e1833ff71798c762e2c95db0e4cf9c93fc6befbaa205c1d365a11e9dd0fc1f1d2c20e662df007c54d858893c13a36ca99ddbe9bb6e37c98dab54714b
+  metadata.gz: d1dab754a4f35b7bb25f86a3d26623c0862d054ee242d11aef7fcdfaadc5ef02eb03bd38c7331542c70921c2d211c69c1afed3960b86a96845f71aeb7c8f4335
+  data.tar.gz: 922f6bc7592ca622417475ceab90c54e1f43cfcf5c7797a1bb10708a19aaf8b1efedcc34857d2067bb22bc6b44af9cafba44bb6024eae7a4943c0418ecd4be88

data/.gitignore

@@ -1,41 +1,41 @@
-.rake_tasks~
-tags
-coverage
-rdoc
-pkg
-test/tmp
-test/version_tmp
-tmp
-pkg
-*.gem
-*.rbc
-lib/bundler/man
-spec/reports
-.config
-InstalledFiles
-.bundle
-
-# YARD artifacts
-.yardoc
-_yardoc
-doc/
-
-.DS_Store
-Icon?
-
-# Thumbnails
-._*
-
-# Files that might appear on external disk
-.Spotlight-V100
-.Trashes
-
-*.swp
-*.swo
-
-Gemfile.lock
-Guardfile
-.rspec
-
-.rvmrc
-.rbenv-gemsets
+.rake_tasks~
+tags
+coverage
+rdoc
+pkg
+test/tmp
+test/version_tmp
+tmp
+pkg
+*.gem
+*.rbc
+lib/bundler/man
+spec/reports
+.config
+InstalledFiles
+.bundle
+
+# YARD artifacts
+.yardoc
+_yardoc
+doc/
+
+.DS_Store
+Icon?
+
+# Thumbnails
+._*
+
+# Files that might appear on external disk
+.Spotlight-V100
+.Trashes
+
+*.swp
+*.swo
+
+Gemfile.lock
+Guardfile
+.rspec
+
+.rvmrc
+.rbenv-gemsets

data/.travis.yml

@@ -1,8 +1,14 @@
 language: ruby
+cache: bundler
 sudo: false
 
+# Early warning system to catch if Rubygems breaks something
+before_install:
+  - gem update --system
+  - gem install bundler
+  - rm -f .bundle/config
+
 rvm:
-  - 2.0.0
   - 2.1
   - 2.2
 script: bundle exec rspec --color --format progress

data/CHANGELOG.md

@@ -2,7 +2,43 @@
 
 Note: this log contains only changes from knife-ec2 release 0.8.0 and later
 -- it does not contain the changes from prior releases. To view change history
-prior to release 0.8.0, please visit the [source repository](https://github.com/opscode/knife-ec2/commits).
+prior to release 0.8.0, please visit the [source repository](https://github.com/chef/knife-ec2/commits).
+
+## Latest Release 0.13.0 (2016-08-05)
+* [knife-ec2:#438](https://github.com/chef/knife-ec2/pull/438) Specs for ec2 server list
+* [knife-ec2:#437](https://github.com/chef/knife-ec2/pull/437) Fix --aws-credential-file issues
+* [knife-ec2:#436](https://github.com/chef/knife-ec2/pull/436) basic is not a valid setting for winrm_ssl_verify_mode
+* [knife-ec2:#435](https://github.com/chef/knife-ec2/pull/435) Fix for Winrm Authentication Failure issue during bootstrap
+* [knife-ec2:#434](https://github.com/chef/knife-ec2/pull/434) Removed ruby2.0.0 from travis
+* [knife-ec2:#431](https://github.com/chef/knife-ec2/pull/431) Pinned rack and ffi-yajl gem to older versions.
+* [knife-ec2:#430](https://github.com/chef/knife-ec2/pull/430) Fixing --aws-config-file issues
+* [knife-ec2:#429](https://github.com/chef/knife-ec2/pull/429) Added validation when spot-wait-mode option is given by user on CLI and spot-price option is not given.
+* [knife-ec2:#428](https://github.com/chef/knife-ec2/pull/428) Fix for s3 secret not getting copied on target vm
+* [knife-ec2:#427](https://github.com/chef/knife-ec2/pull/427) Addedd disable_api_termination option along with RSpecs.
+* [knife-ec2:#416](https://github.com/chef/knife-ec2/pull/416) Modified help for option --security-group-ids
+* [knife-ec2:#409](https://github.com/chef/knife-ec2/pull/409) Passing encrypted\_data\_bag\_secret and encrypted\_databag\_secret\_file
+* [knife-ec2:#405](https://github.com/chef/knife-ec2/pull/405) Updated README file - added description of aws\_config\_file option
+* [knife-ec2:#399](https://github.com/chef/knife-ec2/pull/399) Adding support for aws-config-file
+* [knife-ec2:#400](https://github.com/chef/knife-ec2/pull/400) Added --json-for-attributes-file
+* [knife-ec2:#393](https://github.com/chef/knife-ec2/pull/393) Please also read aws\_session\_token from credentials file - [Richard Morrisey](https://github.com/datascope)
+* [knife-ec2:#395](https://github.com/chef/knife-ec2/pull/395) Fix security groups for spot requests in a VPC and make user input optional - [Mikhail Bautin](https://github.com/mbautin)
+* [knife-ec2:#322](https://github.com/chef/knife-ec2/pull/322) Implement support for ClassicLink [Quention de Metz](https://github.com/quentindemetz)
+* [knife-ec2:#391](https://github.com/chef/knife-ec2/pull/391) adding missing m4,d2,t2,and g2 ebs encryption flavors - [Mario Harvey](https://github.com/badmadrad)
+* [knife-ec2:#390](https://github.com/chef/knife-ec2/pull/390) Modified create\_ssl\_listener option as per Mixlib-CLI.
+* [knife-ec2:#375](https://github.com/chef/knife-ec2/pull/375) Attach network interfaces before bootstrap - [Eric Herot](https://github.com/eherot)
+* [knife-ec2:#389](https://github.com/chef/knife-ec2/pull/389) --server-connect-attribute cleanup
+* [knife-ec2:#388](https://github.com/chef/knife-ec2/pull/388) Updated Readme for --server-connect-attribute option
+* [knife-ec2:#384](https://github.com/chef/knife-ec2/pull/384) server list in json format
+* [knife-ec2:#378](https://github.com/chef/knife-ec2/pull/378) Readme improvements
+* [knife-ec2:#376](https://github.com/chef/knife-ec2/pull/376) Remove instance colors
+* [knife-ec2:#377](https://github.com/chef/knife-ec2/pull/377) Require fog-aws vs. fog
+* [knife-ec2:#368](https://github.com/chef/knife-ec2/pull/368) Handle Errno::ENOTCONN when testing for sshd access - [Eugene Bolshakov](https://github.com/eugenebolshakov)
+* [knife-ec2:#373](https://github.com/chef/knife-ec2/pull/373) Update contributing docs
+* [knife-ec2:#374](https://github.com/chef/knife-ec2/pull/374) Avoid sending nil runlist to Chef::Knife::Boostrap
+* [knife-ec2:#372](https://github.com/chef/knife-ec2/pull/372) Cache gems in travis, update links and opscode -> chef
+* [knife-ec2:#371](https://github.com/chef/knife-ec2/pull/371) fix typo in readme - [Kyle West](https://github.com/kylewest)
+* [knife-ec2:#363](https://github.com/chef/knife-ec2/pull/363) Add ssl config user data for ssl transport, if required append to user\_data script specified by user.
+* [knife-ec2:#319](https://github.com/chef/knife-ec2/pull/319) Pointing docs at itself. This is better then the non-existent chef.io docs.
 
 ## Latest Release: 0.12.0 (2015-10-1)
 
@@ -22,8 +58,8 @@ prior to release 0.8.0, please visit the [source repository](https://github.com/
 * [KNIFE-464](https://tickets.opscode.com/browse/KNIFE-464) Support EC2 STS, i.e. AWS Federation tokens for authentication
 
 ## Release: 0.10.0.rc.1 (2014-10-08)
-* [Issue:#237](https://github.com/opscode/knife-ec2/issues/237) Provide a way to the validation key and data bag secret from S3
-* [Issue:#243](https://github.com/opscode/knife-ec2/issues/243) Support new AWS CLI configuration file format
+* [Issue:#237](https://github.com/chef/knife-ec2/issues/237) Provide a way to the validation key and data bag secret from S3
+* [Issue:#243](https://github.com/chef/knife-ec2/issues/243) Support new AWS CLI configuration file format
 * Update `knife-windows` gem dependency to `knife-windows 0.8.rc.0` for improved Windows authentication integration
 * Update `fog` gem dependency to `fog 1.23.0`
 * Provisioned IOPS support via the `--provisioned-iops` and `--ebs-volume-type` options
@@ -42,7 +78,7 @@ prior to release 0.8.0, please visit the [source repository](https://github.com/
   instance on creation
 
 ## Releases prior to 0.8.0
-Please see <https://github.com/opscode/knife-ec2/commits> to view changes in
+Please see <https://github.com/chef/knife-ec2/commits> to view changes in
 the form of commits to the source repository for releases before 0.8.0.
 
 

data/CONTRIBUTING.md

@@ -1,71 +1,216 @@
-# Contributing to knife-ec2
-
-We are glad you want to contribute to Chef's knife-ec2 plugin! The first step is the desire to improve the project.
-
-You can find the answers to additional frequently asked questions [on the wiki](http://wiki.opscode.com/display/chef/How+to+Contribute).
-
-## Quick-contribute
-
-*   Create an account on our [bug tracker](http://tickets.opscode.com/browse/KNIFE)
-*   Sign our contributor agreement (CLA) [
-online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L)
-    (keep reading if you're contributing on behalf of your employer)
-* Create a ticket for your change on the [bug tracker](http://tickets.opscode.com/browse/KNIFE)
-* Link to your patch as a rebased git branch or pull request from the ticket
-* Resolve the ticket as fixed
-
-We regularly review contributions and will get back to you if we have any suggestions or concerns.
-
-## The Apache License and the CLA/CCLA
-
-Licensing is very important to open source projects, it helps ensure the software continues to be available under the terms that the author desired.
-Chef uses the Apache 2.0 license to strike a balance between open contribution and allowing you to use the software however you would like to.
-
-The license tells you what rights you have that are provided by the copyright holder. It is important that the contributor fully understands what rights
-they are licensing and agrees to them. Sometimes the copyright holder isn't the contributor, most often when the contributor is doing work for a company.
-
-To make a good faith effort to ensure these criteria are met, Opscode requires a Contributor License Agreement (CLA) or a Corporate Contributor License
-Agreement (CCLA) for all contributions. This is without exception due to some matters not being related to copyright and to avoid having to continually
-check with our lawyers about small patches.
-
-It only takes a few minutes to complete a CLA, and you retain the copyright to your contribution.
-
-You can complete our contributor agreement (CLA) [
-online](https://secure.echosign.com/public/hostedForm?formid=PJIF5694K6L).  If you're contributing on behalf of your employer, have
-your employer fill out our [Corporate CLA](https://secure.echosign.com/public/hostedForm?formid=PIE6C7AX856) instead.
-
-## Issue Tracking
-
-You can file tickets to describe the bug you'd like to fix or feature you'd
-like to add via the [knife-ec2 project](http://tickets.opscode.com/browse/KNIFE). For your contribution to be reviewed
-and merged, you **must** file a ticket.
-
-## Contribution Details
-
-Once you've created the ticket, you can make a pull request to
-knife-ec2 on GitHub at <https://github.com/opscode/knife-ec2> that references
-that ticket. 
-
-## Testing Instructions
-
-To run tests, run the following Ruby tool commands from the root of your local checkout of
-knife-ec2:
-
-    bundle install
-    bundle exec rspec spec
-    
-**All tests must pass** before your contribution can be merged. Thus it's a good idea
-to execute the tests without your change to be sure you understand how to run
-them, as well as after to validate that you've avoided regressions.
-
-All but the most trivial changes should include **at least one unit test case** to exercise the
-new / changed code; please add tests to your pull request in this common case.
-
-## Further Resources
-
-### Fog
-
-Knife-ec2 uses the Fog gem to interact with EC2's API. When there's a new
-feature of EC2 that you'd like to utilize in knife-ec2 use cases, that feature
-will probably be exposed by Fog. You can read about Fog
-at its [project page](https://github.com/fog/fog).
+# Contributing to knife-ec2
+
+We're glad you want to contribute to knife-ec2! The first
+step is the desire to improve the project.
+
+## Quick Contributing Steps
+
+1. Create an account on [GitHub](https://github.com).
+2. Create an account on the [Chef Supermarket](https://supermarket.chef.io/).
+3. [Become a contributor](https://supermarket.chef.io/become-a-contributor) by
+signing our Contributor License Agreement (CLA).
+4. Create a pull request for your change on [GitHub](https://github.com/chef/knife-ec2/pulls).
+5. The knife-ec2 maintainers will review your change, and either merge the
+change or offer suggestions.
+
+## The Apache License and the CLA/CCLA
+Licensing is very important to open source projects. It helps ensure the
+software continues to be available under the terms that the author desired.
+
+Chef uses [the Apache 2.0 license](http://www.apache.org/licenses/LICENSE-2.0)
+to strike a balance between open contribution and allowing you to use the
+software however you would like to.
+
+The license tells you what rights you have that are provided by the copyright
+holder. It is important that the contributor fully understands what rights they
+are licensing and agrees to them. Sometimes the copyright holder isn't the
+contributor, such as when the contributor is doing work for a company.
+
+To make a good faith effort to ensure these criteria are met, Chef requires an
+Individual CLA or a Corporate CLA for contributions. This agreement helps ensure
+you are aware of the terms of the license you are contributing your copyrighted
+works under, which helps to prevent the inclusion of works in the projects that
+the contributor does not hold the rights to share.
+
+It only takes a few minutes to complete a CLA, and you retain the copyright to
+your contribution.
+
+You can complete our [Individual
+CLA](https://supermarket.chef.io/icla-signatures/new) online. If you're
+contributing on behalf of your employer and they retain the copyright for your
+works, have your employer fill out our [Corporate
+CLA](https://supermarket.chef.io/ccla-signatures/new) instead.
+
+### Chef Obvious Fix Policy
+
+Small contributions such as fixing spelling errors, where the content is small enough
+  to not be considered intellectual property, can be submitted by a contributor as a patch,
+  without a CLA.
+
+As a rule of thumb, changes are obvious fixes if they do not introduce any new functionality
+  or creative thinking. As long as the change does not affect functionality. Some likely
+  examples include the following:
+
+* Spelling / grammar fixes
+* Typo correction, white space and formatting changes
+* Comment clean up
+* Bug fixes that change default return values or error codes stored in constants
+* Adding logging messages or debugging output
+* Changes to ‘metadata’ files like Gemfile, .gitignore, build scripts, etc.
+* Moving source files from one directory or package to another
+
+**Whenever you invoke the “obvious fix” rule, please say so in your commit message:**
+
+```
+------------------------------------------------------------------------
+commit 370adb3f82d55d912b0cf9c1d1e99b132a8ed3b5
+Author: juliachild <julia@chef.io>
+Date:   Wed Sep 18 11:44:40 2015 -0700
+
+  Fix typo in the README.
+
+  Obvious fix.
+
+------------------------------------------------------------------------
+```
+
+## <a name="issues"></a>Issue Tracking
+
+Chef uses Github Issues to track issues with knife-ec2. Issues should be
+submitted at https://github.com/chef/knife-ec2/issues/new.
+
+In order to decrease the back and forth in issues, and to help us get to
+the bottom of them quickly we use the below issue template. You can copy/paste
+this template into the issue you are opening and edit it accordingly.
+
+<a name="issuetemplate"></a>
+```
+### Environment: [Details about the environment such as the Operating System, Ruby release, etc...]
+
+### Scenario:
+[What you are trying to achieve and you can't?]
+
+
+### Steps to Reproduce:
+[If you are filing an issue what are the things we need to do in order to repro your problem?]
+
+
+### Expected Result:
+[What are you expecting to happen as the consequence of above reproduction steps?]
+
+
+### Actual Result:
+[What actually happens after the reproduction steps?]
+```
+
+## Using git
+
+You can copy the knife-ec2 repository to your local workstation by running
+`git clone git://github.com/chef/knife-ec2.git`.
+
+For collaboration purposes, it is best if you create a GitHub account
+and fork the repository to your own account. Once you do this you will
+be able to push your changes to your GitHub repository for others to
+see and use.
+
+### Branches and Commits
+
+You should submit your patch as a git branch named after the Github
+issue, such as GH-22. This is called a _topic branch_ and allows users
+to associate a branch of code with the ticket.
+
+It is a best practice to have your commit message have a _summary
+line_ that includes the ticket number, followed by an empty line and
+then a brief description of the commit. This also helps other
+contributors understand the purpose of changes to the code.
+
+```text
+    [GH-22] - platform_family and style
+
+    * use platform_family for platform checking
+    * update notifies syntax to "resource_type[resource_name]" instead of
+      resources() lookup
+    * GH-692 - delete config files dropped off by packages in conf.d
+    * dropped debian 4 support because all other platforms have the same
+      values, and it is older than "old stable" debian release
+```
+
+Remember that not all users use Chef in the same way or on the same
+operating systems as you, so it is helpful to be clear about your use
+case and change so they can understand it even when it doesn't apply
+to them.
+
+### More information
+
+Additional help with git is available on the [Community
+Contributions](https://docs.chef.io/community_contributions.html#use-git)
+page on the Chef Docs site.
+
+## Unit Tests
+
+knife-ec2 is tested with rspec unit tests to ensure changes don't cause
+regressions for other use cases. All non-trivial changes must include
+additional unit tests.
+
+To run the rspec tests run the following commands from the root of the
+project:
+
+    bundle install
+    bundle exec rspec spec
+
+**All tests must pass** before your contribution can be merged. Thus it's a good idea
+to execute the tests without your change to be sure you understand how to run
+them, as well as after to validate that you've avoided regressions.
+
+## Code Review
+
+Chef Software regularly reviews code contributions and provides suggestions
+for improvement in the code itself or the implementation.
+
+## Release Cycle
+
+The versioning for Chef Software projects is X.Y.Z.
+
+* X is a major release, which may not be fully compatible with prior
+  major releases
+* Y is a minor release, which adds both new features and bug fixes
+* Z is a patch release, which adds just bug fixes
+
+## Working with the community
+
+These resources will help you learn more about Chef and connect to
+other members of the Chef community:
+
+* [Chef Community Guidelines](https://docs.chef.io/community_guidelines.html)
+* [Chef Mailing List](https://discourse.chef.io/c/dev)
+* #chef and #chef-hacking IRC channels on irc.freenode.net
+* [Supermarket site](https://supermarket.chef.io/)
+* [Chef Docs](http://docs.chef.io)
+* Chef Software Chef [product page](https://www.chef.io/chef/)
+
+
+## Contribution Do's and Don't's
+
+Please do include tests for your contribution. If you need help, ask on the
+[chef-dev mailing list](https://discourse.chef.io/c/dev) or the [#chef-hacking
+IRC channel](https://botbot.me/freenode/chef-hacking/). Please provide
+evidence of testing your contribution if it isn't trivial so we don't have to
+duplicate effort in testing.
+
+Please do **not** modify the version number of the gem, Chef
+will select the appropriate version based on the release cycle
+information above.
+
+Please do **not** update the `CHANGELOG.md` for a new version. Not all
+changes may be merged and released in the same versions. Chef Software
+will update the `CHANGELOG.md` when releasing a new version.
+
+## Further Resources
+
+### Fog
+
+Knife-ec2 uses the Fog gem to interact with EC2's API. When there's a new
+feature of EC2 that you'd like to utilize in knife-ec2 use cases, that feature
+will probably be exposed by Fog. You can read about Fog
+at its [project page](https://github.com/fog/fog).
+