kitchen-sfmc-google 1.2.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: a2b00021fa01bc19c68157cf78dbf8dc3d264b81
+  data.tar.gz: 73f8135f371e193e89ff86b8f8c84f6b86afd9e4
+SHA512:
+  metadata.gz: c02736cec44f9255e4d2c2bddba49108414e8c4cc4714dd5d4325b47d29f910b1ae9e76329eccd2164a5795d079974348cfce6d872e3df9a849691a2be6b119b
+  data.tar.gz: a77ff62e9386134ba1e524e68452a219239dc0078fb59a78846172b9a4db98ae3c0e39225136b220ddadd83c38c164068452af53cb66327aeb3412f11a65106c

data/.gitignore

@@ -0,0 +1,5 @@
+*~
+*#
+.ruby-version
+*.gem
+Gemfile.lock

data/.rubocop.yml

@@ -0,0 +1 @@
+inherit_from: .rubocop_todo.yml

data/.rubocop_todo.yml

@@ -0,0 +1,11 @@
+# This configuration was generated by `rubocop --auto-gen-config`
+# on 2014-09-20 08:00:47 -0700 using RuboCop version 0.26.0.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.
+
+# Offense count: 1
+# Configuration parameters: CountComments.
+Metrics/ClassLength:
+  Max: 102

data/.travis.yml

@@ -0,0 +1,9 @@
+language: ruby
+
+rvm:
+  - 2.0.0
+  - 2.1.0
+  - 2.2
+
+before_install:
+  - gem update bundler

data/CHANGELOG.md

@@ -0,0 +1,97 @@
+## 1.1.0 / 2016-03-17
+
+ * #32: Rubocop and Rake fixes to address Travis test issues
+ * #33: Automatically disable auto-restart and auto-migrate when using preemptible instances
+ * #34: Support for using subnetworks
+ * #35: Support for gcloud-style image aliases (i.e. "centos-7" will get you the latest CentOS image)
+
+## 1.0.0 / 2016-03-10
+
+### New Features
+
+ * #30: use of gcloud authentication files instead of requiring new service accounts
+ * #30: support for service account scope aliases in addition to regular full names/URLs
+ * #30: support for automated public project searching for well-known disk images
+
+### Improvements
+
+ * #30: rewrite using the google-api-client
+ * #30: use of the new Test Kitchen 1.4+ transport plugins
+ * #30: additional user feedback during API interactions
+
+## 0.3.0 / 2016-01-23
+
+### New Features
+
+* #14: Support service_accounts option in Fog
+* #22: Add JSON credential file and Preemptible VM support
+
+### Improvements
+
+* Move to test-kitchen GitHub org
+* Fixes to tests
+
+## 0.2.0 / 2014-09-20
+
+### Improvements
+
+* #10: Deprecate "area" in configuration for "region"
+* #11: Fix name length, via @pdunnavant
+* #12: Generate instance names that are valid for GCE
+
+## 0.1.2 / 2014-04-16
+
+### New Features
+
+* Add documentation for new asia-east1 region.
+
+### Improvements
+
+* #9: Dependency updates: Remove faraday version constraint; require newer 
+  ridley gem.
+
+## 0.1.0 / 2014-03-29
+
+### New Features
+
+* PR #7: Add support for specifying SSH keys in public_key_path, via @someara
+* Add support for setting username
+* Support GCE v1 API, including persistent disks.
+
+### Improvements
+
+* Add rspec tests and Travis support.
+
+## 0.0.6 / 2014-02-23:
+
+* Require Ruby 1.9 or greater.
+
+### Improvements
+
+* Add support for specifying GCE network and tags.
+
+### Bug fixes
+
+* Temporarily pin Fog version to 1.19.0 until 1.20.0 support is added.
+* Require Faraday Gem version to be ~> 0.8.9; 0.9.0 breaks test-kitchen.
+
+## 0.0.4 / 2013-12-28
+
+### Bug fixes
+
+* In GCE, instance names must be unique; derive by default from
+  `<suite>-<platform>` and a UUID.
+* Fix bug where running `kitchen create` multiple times would create
+  duplicate instances.
+* Require version of Fog with exponential backoff in GCE API queries.
+
+### Improvements
+
+* README formatting and clarity fixes.
+* Add concept of an "area" (us, europe, any) to automatically select
+  an availability zone from those that are up within the requested
+  area for each instance.
+
+## 0.0.1 / 2013-10-20
+
+### Initial release

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+# Specify dependencies in gemspec:
+gemspec
+
+gem "chefstyle", git: "https://github.com/chef/chefstyle"

data/LICENSE

@@ -0,0 +1,15 @@
+Author:: Andrew Leonard (<andy@hurricane-ridge.com>)
+
+Copyright (C) 2013-2014, Andrew Leonard
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/README.md

@@ -0,0 +1,345 @@
+# Kitchen::Gce - A Test Kitchen Driver for Google Compute Engine
+
+[![Build Status](https://travis-ci.org/test-kitchen/kitchen-google.png?branch=master)](https://travis-ci.org/test-kitchen/kitchen-google)
+[![Code Climate](https://codeclimate.com/github/test-kitchen/kitchen-google.png)](https://codeclimate.com/github/test-kitchen/kitchen-google)
+
+This is a [Test Kitchen](https://github.com/opscode/test-kitchen/)
+driver for Google Compute Engine.  While similar to EC2 and other IaaS
+providers, GCE has a couple of advantages for Chef cookbook testing:
+
+* (Subjectively) faster instance launch times; and
+* Sub-hour billing.
+
+## Requirements
+
+### Ruby Version
+
+Ruby 2.0 or greater.
+
+### Google Cloud Platform (GCP) Project
+A [Google Cloud Platform](https://cloud.google.com) account is
+required.  If you do not already have an appropriate "project" in
+which to run your test-kitchen instances, create one, noting the
+"project id".
+
+### Authentication and Authorization
+
+The [underlying API](https://github.com/google/google-api-ruby-client) this plugin uses relies on the
+[Google Auth Library](https://github.com/google/google-auth-library-ruby) to handle authentication to the
+Google Cloud API. The auth library expects that there is a JSON credentials file located at:
+
+`~/.config/gcloud/application_default_credentials.json`
+
+The easiest way to create this is to download and install the [Google Cloud SDK](https://cloud.google.com/sdk/) and run the
+`gcloud auth login` command which will create the credentials file for you.
+
+If you already have a file you'd like to use that is in a different location, set the
+`GOOGLE_APPLICATION_CREDENTIALS` environment variable with the full path to that file.
+
+### SSH Keys
+
+In order to bootstrap Linux nodes, you will first need to ensure your SSH
+keys are set up correctly. Ensure your SSH public key is properly entered
+into your project's Metadata tab in the GCP Console. GCE will add your key
+to the appropriate user's `~/.ssh/authorized_keys` file when Chef first
+connects to perform the bootstrap process.
+
+ * If you don't have one, create a key using `ssh-keygen`
+ * Log in to the GCP console, select your project, go to Compute Engine, and go to the Metadata tab.
+ * Select the "SSH Keys" tab.
+ * Add a new item, and paste in your public key.
+    * Note: to change the username automatically detected for the key, prefix your key with the username
+      you plan to use to connect to a new instance. For example, if you plan to connect
+      as "chefuser", your key should look like: `chefuser:ssh-rsa AAAAB3N...`
+ * Click "Save".
+
+Alternatively, the Google Cloud SDK (a.k.a. `gcloud`) will create a SSH key
+for you when you create and access your first instance:
+
+ 1. Create a small test instance:
+    `gcloud compute instances create instance1 --zone us-central1-f --image debian-8 --machine-type g1-small`
+ 1. Ensure your SSH keys allow access to the new instance
+    `gcloud compute ssh instance1 --zone us-central1-f`
+ 1. Log out and delete the instance
+    `gcloud compute instances delete instance1 --zone us-central1-f`
+
+You will now have a local SSH keypair, `~/.ssh/google_compute_engine[.pub]` that
+will be used for connecting to your GCE Linux instances for this local username
+when you use the `gcloud compute ssh` command. You can tell Test Kitchen to use
+this key by adding it to the transport section of your .kitchen.yml:
+
+```yaml
+transport:
+  ssh_key:
+    - ~/.ssh/google_compute_engine
+```
+
+You can find [more information on configuring SSH keys](https://cloud.google.com/compute/docs/instances/adding-removing-ssh-keys) in
+the Google Compute Engine documentation.
+
+## Installation
+
+Install the gem with:
+
+```sh
+gem install kitchen-google
+```
+
+Or, even better, if you're using the ChefDK:
+
+```sh
+chef gem install kitchen-google
+```
+
+If you're using Bundler, simply add it to your Gemfile:
+
+```ruby
+gem "kitchen-google", "~> 1.0"
+```
+
+... and then run `bundle install`.
+
+
+## Configuration
+
+### `project`
+
+**Required**. The project ID of the GCP project into which Test Kitchen
+instances will be launched. This can be found on the "Manage All Projects"
+screen, found under the "Select a Project" drop-down at the top of the
+GCP console.
+
+Note that this parameter requires the "Project ID", not the "Project Name."
+
+Example: "funky-penguin-12345"
+
+### `image_project`
+
+The project ID of the GCP project to search for the configured image or image
+family. This must be specified to find either public images or your own images
+that exist in another project.
+
+Example: "ubuntu-os-cloud"
+
+### `image_family`
+
+The family of the image to initialize your boot disk from, the latest
+non-deprecated image will be used.
+
+Note that this parameter will be ignored if `image_name` is also specified.
+
+Example: "ubuntu-1604-lts"
+
+### `image_name`
+
+The name of the disk image to use as the source image for the boot disk.
+
+Example: `centos-7-v20170124`
+
+This parameter will override `image_family` if they are both specified.
+
+If `image_project` is not specified, only the GCP project specified in `project`
+will be searched.
+
+### `zone`
+
+**Required if `region` is left blank.** The name of the GCE zone in which to
+launch your instances.
+
+Example: `us-east1-b`
+
+### `region`
+
+**Required if zone is left blank.** The name of the region in which to
+launch your instances. A zone in the region will be randomly selected.
+
+Example: `us-central1`
+
+This parameter will be ignored if `zone` is specified.
+
+### `autodelete_disk`
+
+Boolean specifying whether or not to automatically delete boot disk
+for test instance.  Default: `true`
+
+NOTE: If you set this to false, once Test Kitchen destroys your instance,
+the boot disk used will remain in your project. You will need to manually delete it to
+avoid consuming unused resources by either using the `gcloud compute disks delete`
+command in the GCP SDK or by using `knife google disk delete` from
+[knife-google](https://github.com/chef/knife-google).
+
+### `auto_migrate`
+
+Boolean specifying whether or not to automatically migrate the instance
+to a host in the event of host maintenance. Default: `false`
+
+### `disk_size`
+
+Size, in gigabytes, of boot disk.  Default: `10`.
+
+Some images, such as windows images, have a larger source image size
+and require the disk_size to be the same size or larger than the source.
+An error message will be displayed to you indicating this requirement
+if necessary.
+
+### `email`
+
+**Required for Windows instances.** The email address of the
+currently-logged-in GCP user.
+
+While the credentials file specified in the Authentication and Authorization
+section is used for all API interactions, the email address is required when
+performing the necessary password reset prior to bootstrapping the instance.
+
+### `machine_type`
+
+GCE instance type (size) to launch; default: `n1-standard-1`
+
+### `network`
+
+GCE network that instance will be attached to; default: `default`
+
+### `subnet`
+
+GCE subnetwork that instance will be attached to. Only applies to custom networks.
+
+### `preemptible`
+
+If set to `true`, GCE instance will be brought up as a  [preemptible](https://cloud.google.com/compute/docs/instances/preemptible) virtual machine,
+that runs at a much lower price than normal instances. However, Compute
+Engine might terminate (preempt) these instances if it requires access
+to those resources for other tasks; default: `false`
+
+### `service_account_name`
+
+The name of the service account to use when enabling account scopes. This
+is usually an email-formatted service account name created via the "Permissions"
+tab of the GCP console.
+
+This is ignored unless you specify any `service_account_scopes`.
+
+Default: "default"
+
+### `service_account_scopes`
+
+An array of scopes to add to the instance, used to grant additional permissions
+within GCP.
+
+The scopes can either be a full URL (i.e. `https://www.googleapis.com/auth/devstorage.read_write`),
+the short-name (i.e. `devstorage.read_write`), or a gcloud alias (i.e. `storage-rw`).
+
+See the output of `gcloud compute instances create --help` for a full list of scopes.
+
+### `tags`
+
+Array of tags to associate with instance; default: `[]`
+
+### `use_private_ip`
+
+Boolean indicating whether or not to connect to the instance using its
+private IP address. If `true`, kitchen-google will also not provision
+a public IP for this instance. Default: `false`
+
+### `wait_time`
+
+Amount of time, in seconds, to wait for any API interactions. Default: 600
+
+### `refresh_rate`
+
+Amount of time, in seconds, to refresh the status of an API interaction. Default: 2
+
+### Transport Settings
+
+Beginning with Test Kitchen 1.4, settings related to the transport (i.e. how to connect
+to the instance) have been moved to the `transport` section of the config, such as the
+username, password, SSH key path, etc.
+
+Therefore, you will need to update the transport section with the username configured
+for the SSH Key you imported into your project metadata as described in the "SSH Keys"
+section above.  For example, if you are connecting as the "chefuser", your .kitchen.yml
+might have a section like this:
+
+```yaml
+transport:
+  username: chefuser
+```
+
+Additionally, if you do not wish to use the standard default SSH key (`~/.ssh/id_rsa`),
+you can set the `ssh_key` parameter in the `transport` section of your .kitchen.yml.
+For example, if you want to use the SSH key auto-generated by the GCP SDK:
+
+```yaml
+transport:
+  ssh_key:
+    - ~/.ssh/google_compute_engine
+```
+
+## Example .kitchen.yml
+
+```yaml
+---
+driver:
+  name: gce
+  project: mycompany-test
+  zone: us-east1-c
+  email: me@mycompany.com
+  tags:
+    - devteam
+    - test-kitchen
+  service_account_scopes:
+    - devstorage.read_write
+    - userinfo.email
+
+provisioner:
+  name: chef_zero
+
+transport:
+  username: chefuser
+
+platforms:
+  - name: centos-7
+    driver:
+      image_project: centos-cloud
+      image_name: centos-7-v20170124
+  - name: ubuntu-16.04
+    driver:
+      image_project: ubuntu-os-cloud
+      image_family: ubuntu-1604-lts
+  - name: windows
+    driver:
+      image_project: windows-cloud
+      image_name: windows-server-2012-r2-dc-v20170117
+      disk_size: 50
+
+suites:
+  - name: default
+    run_list:
+      - recipe[gcetest::default]
+    attributes:
+```
+
+## Development
+
+Source is hosted on [GitHub](https://github.com/test-kitchen/kitchen-google).
+
+* Pull requests are welcome, using topic branches if possible:
+
+1. Fork the repo.
+2. Create a feature branch, commit changes to it and push them.
+3. Submit a pull request.
+
+* Report issues or submit feature requests on [GitHub](https://github.com/test-kitchen/kitchen-google/issues)
+
+## Author, Acknowledgements, Etc.
+
+Created and maintained by [Andrew Leonard](http://andyleonard.com)
+([andy@hurricane-ridge.com](mailto:andy@hurricane-ridge.com)).
+
+The initial release drew heavily on the
+[kitchen-ec2](https://github.com/opscode/kitchen-ec2/) gem for both
+inspiration and implementation details.  Any bugs, however, are solely
+the author's own doing.
+
+## License
+
+Licensed under Apache 2.0.