vagrant-aws-mkubenka 0.7.2.pre.8

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: dedbb4d147a323c11c9fb699e05644974e543068
+  data.tar.gz: 0ee09e22353f04ff122fbf4ce036141252a7f787
+SHA512:
+  metadata.gz: 6def0553a749fc93e5b5b825ef85b3e0066c62f8ef549afcdfbf0c3920d5f4316c1fb08dc88cb28f67a7d36009d4d647305c64b9d0805fd906453c9227b31244
+  data.tar.gz: 86b8a867cba91d9f6158f0ebaa70c0e787baba496aef867578e70dc973547de69c734e6ee3f010a4d1857d009befdb77274d87c0d0246a6daaf43ec3293a030c

data/.gitignore

@@ -0,0 +1,21 @@
+# OS-specific
+.DS_Store
+
+# editors
+*.swp
+
+# Bundler/Rubygems
+*.gem
+.bundle
+pkg/*
+tags
+Gemfile.lock
+
+# Vagrant
+.vagrant
+Vagrantfile
+!example_box/Vagrantfile
+
+# RVM files for gemset/ruby setting
+.ruby-*
+.rvmrc

data/.rspec

@@ -0,0 +1 @@
+--format doc --order random --color --fail-fast

data/.travis.yml

@@ -0,0 +1,19 @@
+language: ruby
+
+sudo: false
+
+cache: bundler
+
+rvm:
+  - 2.2.7
+  - 2.3.4
+
+deploy:
+  provider: rubygems
+  api_key:
+    secure: A1AYezvoon6JdYHphtrUEeG98r7AtFqsPcETp4BX3sPlSvOghHqco57/JasxFBFbis1irfVxhjqIFaS0lfOO0yxfIJQFnbZ6tTzKJB7IkSWUMuVfGo6qRxnO4vnuodx9Vhh27A7lovuptMCQBDdHXoSPUjgqHacrEzYKLDOarHercnRNRT9mWYR//qFO4RHtQz7hG+6p9tUvGmSeUkXB6AZwDPycPAJgrCd6bRYwlTmID6Jlq07bjcqfTTN+jZzdC22nhgjw2Cao0skcszO3H71DZYeFhoRIA8sMKXnNt7LGtvA2FJFM65bJj3TLVVpDe5Itn/KpSLSwuE9phPpVhv828S98h8pbLVYrhat+2jvNOqwtVw9C0LC9GpPlBcd/8AYuDwEO5a+hdnZ08JnihzqSvQd2XX9XvBiKy/A5mBc5D9bYJ3YXsy6zXToMM0nP8Xr0z3NCEFWtJ3ueGzHVmsZqwdoiH/2g6syx4k1YBHb9zdeGciMdk1vmckPYZJLpGh4cj4bDeIHaGPaZ2tYiBSaQNN+6YEMShQgl1d5k5Du6lHdUKnYR4Z7lvQkjfU73lkDoA9PvZuR7b7yi44stEvsxTpNJCZUZN0JmlXAsGlS3hDpD8/LcJWI6M0y7tBPQ3gEB/3YSAYsAcqJZNZ3wyTuqLPZBPJFr6Prwq3VoMhU=
+  gem: vagrant-aws-mkubenka
+  on:
+    repo: mkubenka/vagrant-aws
+    branch: mkubenka
+    rvm: 2.3.4

data/CHANGELOG.md

@@ -0,0 +1,96 @@
+# 0.6.1
+
+* Added configurable instance state check interval
+
+# 0.6.0 (December 13, 2014)
+
+* Support static Elastic IP addresses.
+* Support for creating AMIs with the `vagrant package`
+
+# 0.5.0 (June 22, 2014)
+
+* Support for associating public IPs for VMs inside of VPCs (GH
+  [#219](https://github.com/mitchellh/vagrant-aws/pull/219), GH
+  [#205](https://github.com/mitchellh/vagrant-aws/issues/205))
+* Bug-fix for per region configs with `associate_public_ip` (GH
+  [#237](https://github.com/mitchellh/vagrant-aws/pull/237))
+* rsyncing folders uses `--delete` flag to better emulate "real shared folders
+  (GH [#194](https://github.com/mitchellh/vagrant-aws/pull/194))
+* fog gem version bumped to 1.22 (GH [#253](https://github.com/mitchellh/vagrant-aws/pull/253))
+* Simple ELB support (GH [#88](https://github.com/mitchellh/vagrant-aws/pull/88),
+  GH [#238](https://github.com/mitchellh/vagrant-aws/pull/238))
+
+# 0.4.1 (December 17, 2013)
+
+* Update fog.io to 1.18.0
+* Fix sync folder user permissions (GH #175)
+* Fix vagrant < 1.3.0 provisioner compatibility (GH #173)
+* Add vagrant 1.4.0 multiple SSH key support (GH #172)
+* Fix EIP deallocation bug (GH #164)
+* Add (per shared folder) rsync exclude flag (GH #156)
+
+# 0.4.0 (October 11, 2013)
+
+* Handle EIP allocation error (GH #134)
+* Implement halt and reload (GH #31)
+* rsync ignores Vagrantfile
+* warn if none of the security groups allows incoming SSH
+* bump fog.io to 1.15.0
+* Fix rsync on windows (GH #77)
+* Add `ssh_host_attribute` config (GH #143)
+
+# 0.3.0 (September 2, 2013)
+
+* Parallelize multi-machine up on Vagrant 1.2+
+* Show proper configuration errors if an invalid configuration key
+  is used.
+* Request confirmation on `vagrant destroy`, like normal VirtualBox + Vagrant.
+* If user data is configured, output is shown on "vagrant up" that
+  it is being set.
+* Add EIP support (GH #65)
+* Add block device mapping support (GH #93)
+* README improvements (GH #120)
+* Fix missing locale message (GH #73)
+* SyncFolders creates hostpath if it doesn't exist and `:create` option is set (GH #17)
+* Add IAM Instance Profile support (GH #68)
+* Add shutdown behavior support (GH #125,#131)
+
+# 0.2.2 (April 18, 2013)
+
+* Fix crashing bug with incorrect provisioner arguments.
+
+# 0.2.1 (April 16, 2013)
+
+* Got rid of extranneous references to old SSH settings.
+
+# 0.2.0 (April 16, 2013)
+
+* Add support for `vagrant ssh -c` [GH-42]
+* Ability to specify a timeout for waiting for instances to become ready. [GH-44]
+* Better error message if instance didn't become ready in time.
+* Connection can now be done using IAM profiles. [GH-41]
+
+# 0.1.3 (April 9, 2013)
+
+* The `AWS_ACCESS_KEY` and `AWS_SECRET_KEY` will be used if available
+  and no specific keys are set in the Vagrantfile. [GH-33]
+* Fix issues with SSH on VPCs, the correct IP is used. [GH-30]
+* Exclude the ".vagrant" directory from rsync.
+* Implement `:disabled` flag support for shared folders. [GH-29]
+* `aws.user_data` to specify user data on the instance. [GH-26]
+
+# 0.1.2 (March 22, 2013)
+
+* Choose the proper region when connecting to AWS. [GH-9]
+* Configurable SSH port. [GH-13]
+* Support other AWS-compatible API endpoints with `config.endpoint`
+  and `config.version`. [GH-6]
+* Disable strict host key checking on rsync so known hosts aren't an issue. [GH-7]
+
+# 0.1.1 (March 18, 2013)
+
+* Up fog dependency for Vagrant 1.1.1
+
+# 0.1.0 (March 14, 2013)
+
+* Initial release.

data/Gemfile

@@ -0,0 +1,12 @@
+source "https://rubygems.org"
+
+group :development do
+  # We depend on Vagrant for development, but we don't add it as a
+  # gem dependency because we expect to be installed within the
+  # Vagrant environment itself using `vagrant plugin`.
+  gem "vagrant", :git => "https://github.com/mitchellh/vagrant.git"
+end
+
+group :plugins do
+  gemspec
+end

data/LICENSE

@@ -0,0 +1,8 @@
+The MIT License (MIT)
+Copyright (c) 2014 Mitchell Hashimoto
+
+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

@@ -0,0 +1,326 @@
+# Vagrant AWS Provider
+[![Gitter](https://badges.gitter.im/Join Chat.svg)](https://gitter.im/mitchellh/vagrant-aws?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
+
+<span class="badges">
+[![Gem Version](https://badge.fury.io/rb/vagrant-aws.png)][gem]
+[![Dependency Status](https://gemnasium.com/mitchellh/vagrant-aws.png)][gemnasium]
+</span>
+
+[gem]: https://rubygems.org/gems/vagrant-aws
+[gemnasium]: https://gemnasium.com/mitchellh/vagrant-aws
+
+This is a [Vagrant](http://www.vagrantup.com) 1.2+ plugin that adds an [AWS](http://aws.amazon.com)
+provider to Vagrant, allowing Vagrant to control and provision machines in
+EC2 and VPC.
+
+**NOTE:** This plugin requires Vagrant 1.2+,
+
+## Features
+
+* Boot EC2 or VPC instances.
+* SSH into the instances.
+* Provision the instances with any built-in Vagrant provisioner.
+* Minimal synced folder support via `rsync`.
+* Define region-specific configurations so Vagrant can manage machines
+  in multiple regions.
+* Package running instances into new vagrant-aws friendly boxes
+
+## Usage
+
+Install using standard Vagrant 1.1+ plugin installation methods. After
+installing, `vagrant up` and specify the `aws` provider. An example is
+shown below.
+
+```
+$ vagrant plugin install vagrant-aws
+...
+$ vagrant up --provider=aws
+...
+```
+
+Of course prior to doing this, you'll need to obtain an AWS-compatible
+box file for Vagrant.
+
+## Quick Start
+
+After installing the plugin (instructions above), the quickest way to get
+started is to actually use a dummy AWS box and specify all the details
+manually within a `config.vm.provider` block. So first, add the dummy
+box using any name you want:
+
+```
+$ vagrant box add dummy https://github.com/mitchellh/vagrant-aws/raw/master/dummy.box
+...
+```
+
+And then make a Vagrantfile that looks like the following, filling in
+your information where necessary.
+
+```
+Vagrant.configure("2") do |config|
+  config.vm.box = "dummy"
+
+  config.vm.provider :aws do |aws, override|
+    aws.access_key_id = "YOUR KEY"
+    aws.secret_access_key = "YOUR SECRET KEY"
+    aws.session_token = "SESSION TOKEN"
+    aws.keypair_name = "KEYPAIR NAME"
+
+    aws.ami = "ami-7747d01e"
+
+    override.ssh.username = "ubuntu"
+    override.ssh.private_key_path = "PATH TO YOUR PRIVATE KEY"
+  end
+end
+```
+
+And then run `vagrant up --provider=aws`.
+
+This will start an Ubuntu 12.04 instance in the us-east-1 region within
+your account. And assuming your SSH information was filled in properly
+within your Vagrantfile, SSH and provisioning will work as well.
+
+Note that normally a lot of this boilerplate is encoded within the box
+file, but the box file used for the quick start, the "dummy" box, has
+no preconfigured defaults.
+
+If you have issues with SSH connecting, make sure that the instances
+are being launched with a security group that allows SSH access.
+
+Note: if you don't configure `aws.access_key_id` or `aws_secret_access_key`
+it will attempt to read credentials from environment variables first and then
+from `$HOME/.aws/`. You can choose your AWS profile and files location by using
+`aws.aws_profile` and `aws.aws_dir`, however environment variables will always
+have precedence as defined by the [AWS documentation](http://docs.aws.amazon.com/cli/latest/userguide/cli-chap-getting-started.html).
+To use profile `vagrantDev` from your AWS files:
+```ruby
+  # this first line can actually be omitted
+  aws.aws_dir = ENV['HOME'] + "/.aws/"
+  aws.aws_profile = "vagrantDev"
+```
+
+
+## Box Format
+
+Every provider in Vagrant must introduce a custom box format. This
+provider introduces `aws` boxes. You can view an example box in
+the [example_box/ directory](https://github.com/mitchellh/vagrant-aws/tree/master/example_box).
+That directory also contains instructions on how to build a box.
+
+The box format is basically just the required `metadata.json` file
+along with a `Vagrantfile` that does default settings for the
+provider-specific configuration for this provider.
+
+## Configuration
+
+This provider exposes quite a few provider-specific configuration options:
+
+* `access_key_id` - The access key for accessing AWS
+* `ami` - The AMI id to boot, such as "ami-12345678"
+* `availability_zone` - The availability zone within the region to launch
+  the instance. If nil, it will use the default set by Amazon.
+* `aws_profile` - AWS profile in your config files. Defaults to *default*.
+* `aws_dir` - AWS config and credentials location. Defaults to *$HOME/.aws/*.
+* `instance_ready_timeout` - The number of seconds to wait for the instance
+  to become "ready" in AWS. Defaults to 120 seconds.
+* `instance_check_interval` - The number of seconds to wait to check the instance's
+ state
+* `instance_package_timeout` - The number of seconds to wait for the instance
+  to be burnt into an AMI during packaging. Defaults to 600 seconds.
+* `instance_type` - The type of instance, such as "m3.medium". The default
+  value of this if not specified is "m3.medium".  "m1.small" has been
+  deprecated in "us-east-1" and "m3.medium" is the smallest instance
+  type to support both paravirtualization and hvm AMIs
+* `keypair_name` - The name of the keypair to use to bootstrap AMIs
+   which support it.
+* `monitoring` - Set to "true" to enable detailed monitoring.
+* `session_token` - The session token provided by STS
+* `private_ip_address` - The private IP address to assign to an instance
+  within a [VPC](http://aws.amazon.com/vpc/)
+* `elastic_ip` - Can be set to 'true', or to an existing Elastic IP address. 
+  If true, allocate a new Elastic IP address to the instance. If set
+  to an existing Elastic IP address, assign the address to the instance.
+* `region` - The region to start the instance in, such as "us-east-1"
+* `secret_access_key` - The secret access key for accessing AWS
+* `security_groups` - An array of security groups for the instance. If this
+  instance will be launched in VPC, this must be a list of security group
+  Name. For a nondefault VPC, you must use security group IDs instead (http://docs.aws.amazon.com/cli/latest/reference/ec2/run-instances.html).
+* `iam_instance_profile_arn` - The Amazon resource name (ARN) of the IAM Instance
+    Profile to associate with the instance
+* `iam_instance_profile_name` - The name of the IAM Instance Profile to associate
+  with the instance
+* `subnet_id` - The subnet to boot the instance into, for VPC.
+* `associate_public_ip` - If true, will associate a public IP address to an instance in a VPC.
+* `ssh_host_attribute` - If `:public_ip_address`, `:dns_name`, or
+  `:private_ip_address`, will use the public IP address, DNS name, or private
+  IP address, respectively, to SSH to the instance. By default Vagrant uses the
+  first of these (in this order) that is known. However, this can lead to
+  connection issues if, e.g., you are assigning a public IP address but your
+  security groups prevent public SSH access and require you to SSH in via the
+  private IP address; specify `:private_ip_address` in this case.
+* `tenancy` - When running in a VPC configure the tenancy of the instance.  Supports 'default' and 'dedicated'.
+* `tags` - A hash of tags to set on the machine.
+* `package_tags` - A hash of tags to set on the ami generated during the package operation.
+* `use_iam_profile` - If true, will use [IAM profiles](http://docs.aws.amazon.com/IAM/latest/UserGuide/instance-profiles.html)
+  for credentials.
+* `block_device_mapping` - Amazon EC2 Block Device Mapping Property
+* `elb` - The ELB name to attach to the instance.
+* `unregister_elb_from_az` - Removes the ELB from the AZ on removal of the last instance if true (default). In non default VPC this has to be false.
+* `terminate_on_shutdown` - Indicates whether an instance stops or terminates
+  when you initiate shutdown from the instance.
+* `endpoint` - The endpoint URL for connecting to AWS (or an AWS-like service). Only required for non AWS clouds, such as [eucalyptus](https://github.com/eucalyptus/eucalyptus/wiki).
+
+These can be set like typical provider-specific configuration:
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider :aws do |aws|
+    aws.access_key_id = "foo"
+    aws.secret_access_key = "bar"
+  end
+end
+```
+
+Note that you do not have to hard code your `aws.access_key_id` or `aws.secret_access_key`
+as they will be retrieved from the enviornment variables `AWS_ACCESS_KEY` and `AWS_SECRET_KEY`.
+
+In addition to the above top-level configs, you can use the `region_config`
+method to specify region-specific overrides within your Vagrantfile. Note
+that the top-level `region` config must always be specified to choose which
+region you want to actually use, however. This looks like this:
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider :aws do |aws|
+    aws.access_key_id = "foo"
+    aws.secret_access_key = "bar"
+    aws.region = "us-east-1"
+
+    # Simple region config
+    aws.region_config "us-east-1", :ami => "ami-12345678"
+
+    # More comprehensive region config
+    aws.region_config "us-west-2" do |region|
+      region.ami = "ami-87654321"
+      region.keypair_name = "company-west"
+    end
+  end
+end
+```
+
+The region-specific configurations will override the top-level
+configurations when that region is used. They otherwise inherit
+the top-level configurations, as you would probably expect.
+
+## Networks
+
+Networking features in the form of `config.vm.network` are not
+supported with `vagrant-aws`, currently. If any of these are
+specified, Vagrant will emit a warning, but will otherwise boot
+the AWS machine.
+
+## Synced Folders
+
+There is minimal support for synced folders. Upon `vagrant up`,
+`vagrant reload`, and `vagrant provision`, the AWS provider will use
+`rsync` (if available) to uni-directionally sync the folder to
+the remote machine over SSH.
+
+See [Vagrant Synced folders: rsync](https://docs.vagrantup.com/v2/synced-folders/rsync.html)
+
+
+## Other Examples
+
+### Tags
+
+To use tags, simply define a hash of key/value for the tags you want to associate to your instance, like:
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider "aws" do |aws|
+    aws.tags = {
+	  'Name' => 'Some Name',
+	  'Some Key' => 'Some Value'
+    }
+  end
+end
+```
+
+### User data
+
+You can specify user data for the instance being booted.
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider "aws" do |aws|
+    # Option 1: a single string
+    aws.user_data = "#!/bin/bash\necho 'got user data' > /tmp/user_data.log\necho"
+
+    # Option 2: use a file
+    aws.user_data = File.read("user_data.txt")
+  end
+end
+```
+
+### Disk size
+
+Need more space on your instance disk? Increase the disk size.
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider "aws" do |aws|
+    aws.block_device_mapping = [{ 'DeviceName' => '/dev/sda1', 'Ebs.VolumeSize' => 50 }]
+  end
+end
+```
+
+### ELB (Elastic Load Balancers)
+
+You can automatically attach an instance to an ELB during boot and detach on destroy.
+
+```ruby
+Vagrant.configure("2") do |config|
+  # ... other stuff
+
+  config.vm.provider "aws" do |aws|
+    aws.elb = "production-web"
+  end
+end
+```
+
+## Development
+
+To work on the `vagrant-aws` plugin, clone this repository out, and use
+[Bundler](http://gembundler.com) to get the dependencies:
+
+```
+$ bundle
+```
+
+Once you have the dependencies, verify the unit tests pass with `rake`:
+
+```
+$ bundle exec rake
+```
+
+If those pass, you're ready to start developing the plugin. You can test
+the plugin without installing it into your Vagrant environment by just
+creating a `Vagrantfile` in the top level of this directory (it is gitignored)
+and add the following line to your `Vagrantfile` 
+```ruby
+Vagrant.require_plugin "vagrant-aws"
+```
+Use bundler to execute Vagrant:
+```
+$ bundle exec vagrant up --provider=aws
+```