jets 0.5.0 → 0.5.1

data/vendor/dynomite/spec/spec_helper.rb

@@ -0,0 +1,110 @@
+ENV['DYNOMITE_ENV'] = 'test'
+ENV['DYNOMITE_CONFIG'] = 'spec/fixtures/app_root/config/dynamodb.yml'
+ENV['JETS_ROOT'] = 'spec/fixtures'
+
+root = File.expand_path("../../", __FILE__)
+require "#{root}/lib/dynomite"
+
+require "pp"
+require "fileutils"
+
+# This file was generated by the `rspec --init` command. Conventionally, all
+# specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.
+# The generated `.rspec` file contains `--require spec_helper` which will cause
+# this file to always be loaded, without a need to explicitly require it in any
+# files.
+#
+# Given that it is always loaded, you are encouraged to keep this file as
+# light-weight as possible. Requiring heavyweight dependencies from this file
+# will add to the boot time of your test suite on EVERY test run, even for an
+# individual file that may not need all of that loaded. Instead, consider making
+# a separate helper file that requires the additional dependencies and performs
+# the additional setup, and require it from the spec files that actually need
+# it.
+#
+# See http://rubydoc.info/gems/rspec-core/RSpec/Core/Configuration
+RSpec.configure do |config|
+  # rspec-expectations config goes here. You can use an alternate
+  # assertion/expectation library such as wrong or the stdlib/minitest
+  # assertions if you prefer.
+  config.expect_with :rspec do |expectations|
+    # This option will default to `true` in RSpec 4. It makes the `description`
+    # and `failure_message` of custom matchers include text for helper methods
+    # defined using `chain`, e.g.:
+    #     be_bigger_than(2).and_smaller_than(4).description
+    #     # => "be bigger than 2 and smaller than 4"
+    # ...rather than:
+    #     # => "be bigger than 2"
+    expectations.include_chain_clauses_in_custom_matcher_descriptions = true
+  end
+
+  # rspec-mocks config goes here. You can use an alternate test double
+  # library (such as bogus or mocha) by changing the `mock_with` option here.
+  config.mock_with :rspec do |mocks|
+    # Prevents you from mocking or stubbing a method that does not exist on
+    # a real object. This is generally recommended, and will default to
+    # `true` in RSpec 4.
+    mocks.verify_partial_doubles = true
+  end
+
+  # This option will default to `:apply_to_host_groups` in RSpec 4 (and will
+  # have no way to turn it off -- the option exists only for backwards
+  # compatibility in RSpec 3). It causes shared context metadata to be
+  # inherited by the metadata hash of host groups and examples, rather than
+  # triggering implicit auto-inclusion in groups with matching metadata.
+  config.shared_context_metadata_behavior = :apply_to_host_groups
+
+# The settings below are suggested to provide a good initial experience
+# with RSpec, but feel free to customize to your heart's content.
+=begin
+  # This allows you to limit a spec run to individual examples or groups
+  # you care about by tagging them with `:focus` metadata. When nothing
+  # is tagged with `:focus`, all examples get run. RSpec also provides
+  # aliases for `it`, `describe`, and `context` that include `:focus`
+  # metadata: `fit`, `fdescribe` and `fcontext`, respectively.
+  config.filter_run_when_matching :focus
+
+  # Allows RSpec to persist some state between runs in order to support
+  # the `--only-failures` and `--next-failure` CLI options. We recommend
+  # you configure your source control system to ignore this file.
+  config.example_status_persistence_file_path = "spec/examples.txt"
+
+  # Limits the available syntax to the non-monkey patched syntax that is
+  # recommended. For more details, see:
+  #   - http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/
+  #   - http://www.teaisaweso.me/blog/2013/05/27/rspecs-new-message-expectation-syntax/
+  #   - http://rspec.info/blog/2014/05/notable-changes-in-rspec-3/#zero-monkey-patching-mode
+  config.disable_monkey_patching!
+
+  # This setting enables warnings. It's recommended, but in some cases may
+  # be too noisy due to issues in dependencies.
+  config.warnings = true
+
+  # Many RSpec users commonly either run the entire suite or an individual
+  # file, and it's useful to allow more verbose output when running an
+  # individual spec file.
+  if config.files_to_run.one?
+    # Use the documentation formatter for detailed output,
+    # unless a formatter has already been configured
+    # (e.g. via a command-line flag).
+    config.default_formatter = "doc"
+  end
+
+  # Print the 10 slowest examples and example groups at the
+  # end of the spec run, to help surface which specs are running
+  # particularly slow.
+  config.profile_examples = 10
+
+  # Run specs in random order to surface order dependencies. If you find an
+  # order dependency and want to debug it, you can fix the order by providing
+  # the seed, which is printed after each run.
+  #     --seed 1234
+  config.order = :random
+
+  # Seed global randomization in this process using the `--seed` CLI option.
+  # Setting this allows you to use `--seed` to deterministically reproduce
+  # test failures related to randomization by passing the same `--seed` value
+  # as the one that triggered the failure.
+  Kernel.srand config.seed
+=end
+end

data/vendor/lambdagem/CHANGELOG.md

@@ -0,0 +1,24 @@
+# Change Log
+
+All notable changes to this project will be documented in this file.
+This project *tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
+
+## [0.5.0]
+- add lambdagem_url support
+
+## [0.4.0]
+- use jets ruby version 2.5.0 for 2.5.x ruby variants
+- fix lambdagem ruby extraction
+
+## [0.3.0]
+- default to lambdagems bucket
+- allow extracting different ruby versions easily
+- tidy up and remove unnecessary files from gems after building
+- add lambda exist class: useful as an ruby api
+
+## [0.2.1]
+- Fix gemspec.
+
+## [0.2.0]
+- Initial release.
+- lambdagem build, package, upload, all extract_gem, extract_ruby, clean commands

data/vendor/lambdagem/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+# Specify your gem dependencies in lambdagem.gemspec
+gemspec
+
+gem "codeclimate-test-reporter", group: :test, require: nil

data/vendor/lambdagem/Gemfile.lock

@@ -0,0 +1,73 @@
+PATH
+  remote: .
+  specs:
+    lambdagem (0.5.0)
+      aws-sdk-s3
+      colorize
+      gems
+      hashie
+      thor
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    aws-eventstream (1.0.1)
+    aws-partitions (1.98.0)
+    aws-sdk-core (3.24.0)
+      aws-eventstream (~> 1.0)
+      aws-partitions (~> 1.0)
+      aws-sigv4 (~> 1.0)
+      jmespath (~> 1.0)
+    aws-sdk-kms (1.7.0)
+      aws-sdk-core (~> 3)
+      aws-sigv4 (~> 1.0)
+    aws-sdk-s3 (1.17.0)
+      aws-sdk-core (~> 3, >= 3.21.2)
+      aws-sdk-kms (~> 1)
+      aws-sigv4 (~> 1.0)
+    aws-sigv4 (1.0.3)
+    byebug (10.0.2)
+    codeclimate-test-reporter (1.0.8)
+      simplecov (<= 0.13)
+    colorize (0.8.1)
+    diff-lcs (1.3)
+    docile (1.1.5)
+    gems (1.1.1)
+      json
+    hashie (3.6.0)
+    jmespath (1.4.0)
+    json (2.1.0)
+    rake (12.3.1)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.0)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.0)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.0)
+    simplecov (0.13.0)
+      docile (~> 1.1.0)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.2)
+    thor (0.20.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler
+  byebug
+  codeclimate-test-reporter
+  lambdagem!
+  rake
+  rspec
+
+BUNDLED WITH
+   1.16.3

data/vendor/lambdagem/Guardfile

@@ -0,0 +1,12 @@
+guard "rspec" do
+  watch(%r{^spec/.+_spec\.rb$})
+  watch(%r{^lib/(.+)\.rb$})      { "spec/lambdagem_spec.rb" }
+  watch(%r{^lib/lambdagem/(.+)\.rb$})  { "spec/lambdagem_spec.rb" }
+  watch("spec/spec_helper.rb")   { "spec/lambdagem_spec.rb" }
+  watch(%r{^lib/lambdagem/(.+)\.rb$})   { |m| "spec/lib/#{m[1]}_spec.rb" }
+end
+
+guard "bundler" do
+  watch("Gemfile")
+  watch(/^.+\.gemspec/)
+end

data/vendor/lambdagem/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2013 Tung Nguyen
+
+MIT License
+
+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/vendor/lambdagem/README.md

@@ -0,0 +1,143 @@
+# Lambdagem
+
+Tool to manage gems designed for AWS Lambda. Some gems require compiled binary dependencies. Lambdagem is useful for handling these types of gems.  This tool does the following:
+
+* Builds, packages, and uploads a gem artifact to s3.
+* Downloads and extracts the gem from s3 in a consistent fashion.
+
+## Summary
+
+Summary of the important folders and files:
+
+Folder  | Description
+------------- | -------------
+/tmp/lambdagem  | Original area where gem is built.  You can find the generated Gemfile in here.
+/tmp/lambdagem/bundled/gems  | Where built gems are vendored.
+/tmp/lambdagem/artifacts/byebug-9.1.0/bundled  | Folder where the slimmed version of the artifacts are copied over.  Care is taken to include only the necessary files to keep the size small.
+/tmp/lambdagem/artifacts/byebug-9.1.0-x86_64-linux.tgz  |  The created tarball.  The tarball contains "bundled" folder which contain the original underlying folder structure.
+s3://lambdagems/gems/2.5.0/byebug/byebug-9.1.0-x86_64-linux.tgz  | Example bucket path where the tarball gets uploaded.  The tgz file contains the containing `bundled` folder.
+
+## Usage
+
+### Build Gem
+
+The build command should be run on an AWS Lambda AMI EC2 instance. To build the latest version of a gem:
+
+```sh
+lambdagem build byebug
+```
+
+The gem gets built in the `/tmp/lambdagem` folder and is vendored to `/tmp/lambdagem/bundled/gems`. The `/tmp/lambdagem` folder is cleared out at the beginning of each run. To build a specific version append the version to the name like so:
+
+```sh
+lambdagem build byebug-0.9.1
+```
+
+The build command produces a `bundled` folder containing the gem and any compiled .so extensions belonging to the gem.
+
+The bundled folder does not include system library files outside of the gem. The bundled folder is left in place though so that additional scripts can add system library dependencies to the same bundled folder.  If there are no system dependencies to be added, move onto creating the tarball package.
+
+To package up the bundled folder into a tarball:
+
+```sh
+lambda package byebug
+```
+
+The package command produces a compressed tarball that contains the bundled folder and its binary extensions. Lambdagem temporarily stores the tarball at:
+
+```
+/tmp/lambdagem/artifacts/byebug-9.1.0-x86_64-linux.tar.gz
+```
+
+Next, upload to s3:
+
+```sh
+lambdagem upload byebug --s3 S3_BUCKET
+```
+
+The file will be uploaded to s3 with this path structure:
+
+```
+s3://S3_BUCKET/gems/MINOR_RUBY_VERSION/byebug/byebug-9.1.0-x86_64-linux.tgz
+```
+
+Gems uploaded to s3 are public-read by default.  You can override this behavior by setting the environment variable `LAMBDAGEM_S3_ACL=private`.
+
+### Extract Gem
+
+The extract command can be run from any environment. Though the extracted gems will only work in an AWS Lambda Linux based environment.
+
+The `--s3` option is required for the extract command. Here's an example how you would download a gem from s3 and extracts it in a standard way:
+
+```sh
+lambdagem extract byebug-0.9.1 --s3 lambdagems
+```
+
+This extracts the gem and produces a top-level `bundled` folder.  This bundled folded is meant to be added to your project folder.
+
+AWS Lambda extracts your code to `/var/task` so this will result in producing a final `/var/task/bundled` folder in the Lambda environment.
+
+# Concepts to Understand
+
+To understand how this tool works it is helpful to see how ruby structures gems on the file system.  The `lambdagem build` command makes a lot more sense when you understand the underlying structure.
+
+## Bundling
+
+There are 2 important folders to under the `bundled/gems` folder: gems and extensions.  Here are their paths with some helpful surrounding context:
+
+* bundled/gems/ruby/2.5.0/gems/byebug-9.1.0
+* bundled/gems/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/byebug-9.1.0
+
+Here are the relevant parts of the tree structure to help further understand:
+
+```sh
+$ tree -L 4 bundled/gems/ruby/2.5.0 # deleted some info to keep short
+bundled/gems/ruby/2.5.0
+├── extensions
+│   └── x86_64-linux
+│       └── 2.5.0-static
+│          └── byebug-9.1.0
+│── gems
+│    └── byebug-9.1.0
+└── specifications
+$
+```
+
+So the strategy we'll employ is to tarball up the relevant gem folders from underneath the `bundled/gems/ruby/2.5.0` folder:
+
+* 2.5.0/gems/byebug-9.1.0
+* 2.5.0/extensions/x86_64-linux/2.5.0-static/byebug-9.1.0
+* 2.5.0/specifications
+
+We will then be able to extract the `bundled` folder and reproduce the `bundled/gems/ruby` path structure.
+
+The tarball could be named `bundled.tgz` to be consistent with the `bundled` folder that is packaged up, but we elect to name the file with the gem info instead, example: `byebug-9.1.0-x86_64-linux.tgz`.
+
+## S3 Uploaded Path
+
+The `byebug-9.1.0-x86_64-linux.tgz` file gets uploaded to s3 at following path:
+
+* s3://S3_BUCKET/gems/2.5.0/byebug/byebug-9.1.0-x86_64-linux.tgz
+
+### Gem Extraction
+
+To extract the gem and restore the directory structure, you can use the `lambdagem extract` command.  Also understanding the underlying folder structure helps make clear what the `lambdagem extract` command does.
+
+Reminder that 2 important folders to under the `bundled/gems/ruby/2.5.0` folder are: gems, extensions and specifications.  Here are their paths with some helpful surrounding context:
+
+* bundled/gems/ruby/2.5.0/gems/byebug-9.1.0
+* bundled/gems/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/byebug-9.1.0
+* specifications
+
+The `lambdagem extract` command should be run at the root of the project because it contains files for `bundled` folder with the original path structure.
+
+Lambdagem will untar the file and **replace** the relevant folders under the `bundle/gems/ruby/2.5.0` folder.  For example, the existing gem folders will be deleted and replaced entirely:
+
+* bundled/gems/ruby/2.5.0/gems/byebug-9.1.0
+* bundled/gems/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/byebug-9.1.0
+
+Only the gem the `byebug-9.1.0` gem folders get replaced, the other gems are left alone.  Extra system dependencies added under the `bundled` folder are also left untouched.
+
+## Lambda Gem Build Stages Diagram
+
+https://docs.google.com/drawings/d/10bEe2NrCwI4paliJdJ3XVbQhyI4XPCc9fwN0EV7e6U0/edit

data/vendor/lambdagem/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+task :default => :spec
+
+RSpec::Core::RakeTask.new

data/vendor/lambdagem/bundled/gems/ruby/2.5.0/extensions/x86_64-linux/2.5.0-static/byebug-10.0.0/gem_make.out

@@ -0,0 +1,19 @@
+current directory: /tmp/lambdagem/bundled/gems/ruby/2.5.0/gems/byebug-10.0.0/ext/byebug
+/var/task/bundled/rbenv/versions/2.5.0/bin/ruby -r ./siteconf20180129-3007-1s55vnf.rb extconf.rb
+creating Makefile
+
+current directory: /tmp/lambdagem/bundled/gems/ruby/2.5.0/gems/byebug-10.0.0/ext/byebug
+make "DESTDIR=" clean
+
+current directory: /tmp/lambdagem/bundled/gems/ruby/2.5.0/gems/byebug-10.0.0/ext/byebug
+make "DESTDIR="
+compiling breakpoint.c
+compiling byebug.c
+compiling context.c
+compiling locker.c
+compiling threads.c
+linking shared-object byebug/byebug.so
+
+current directory: /tmp/lambdagem/bundled/gems/ruby/2.5.0/gems/byebug-10.0.0/ext/byebug
+make "DESTDIR=" install
+/usr/bin/install -c -m 0755 byebug.so ./.gem.20180129-3007-vsab69/byebug

data/vendor/lambdagem/bundled/gems/ruby/2.5.0/gems/byebug-10.0.0/LICENSE

@@ -0,0 +1,23 @@
+Copyright (c) David Rodríguez <deivid.rodriguez@gmail.com>
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+1. Redistributions of source code must retain the above copyright
+   notice, this list of conditions and the following disclaimer.
+2. Redistributions in binary form must reproduce the above copyright
+   notice, this list of conditions and the following disclaimer in the
+   documentation and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGE.