jets 0.5.0 → 0.5.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6c51b1f5b79f92cc5757f4305ab39cc9ea7adb0bdbe1342de962f9aa9bf1a0a2
-  data.tar.gz: a58d4a440dd3056f5128976ac90721bbaa3fde485538fc0cf46727731d414fe2
+  metadata.gz: b26c22c243a758a2e9484da3542193cd2b4c15872db4a7478f815ba4ff0c5684
+  data.tar.gz: 72aee61e4d0af2adeec467061b9f799275b861c079e450a47d47d3e362eac935
 SHA512:
-  metadata.gz: d6aa5ae72821bf10b89f128bf58e22a0ee568e0d45b706a4369d334c94d6a7072246f1390097351f5d2f62c4dbfc91e5166cc10b53196e658a6c03e8b92a3b61
-  data.tar.gz: '099f0a7ea58d4e7809f38c6d7bcca84a7a1f24c884a0ce0b2a0d52b9be66c876ded1220c63d60628ee85f72f3760bd9d29e91138acfb136d59d2255c995353b4'
+  metadata.gz: d10c037571d85fd15e3a70a3e962b7d8ed3f0112baea22b0e829eba1b278e54fe615fcbda7ba8e8af79c6761b377893fb92d098a600077bd7f87fcb7f23d2af7
+  data.tar.gz: df7dc5138ba794386182bf3385914cc70a0abda0bd9bdf4014816b38defcb467ae4ff30ec3728639a01bd975f4eceaa5f69493c2c836c1bfdd389b4fbb3bd88b

data/.codebuild/scripts/install-java.sh

@@ -13,8 +13,10 @@ java -XshowSettings:properties -version
 
 ###
 # maven install: https://maven.apache.org/install.html
-wget http://mirror.cogentco.com/pub/apache/maven/maven-3/3.5.3/binaries/apache-maven-3.5.3-bin.tar.gz
-tar zxf apache-maven-3.5.3-bin.tar.gz
-mkdir -p /opt
-mv apache-maven-3.5.3 /opt/maven
-ln -s /opt/maven/bin/mvn /usr/local/bin/mvn
+#
+# maven url is down, comment out since we're not using maven
+# wget http://mirror.cogentco.com/pub/apache/maven/maven-3/3.5.3/binaries/apache-maven-3.5.3-bin.tar.gz
+# tar zxf apache-maven-3.5.3-bin.tar.gz
+# mkdir -p /opt
+# mv apache-maven-3.5.3 /opt/maven
+# ln -s /opt/maven/bin/mvn /usr/local/bin/mvn

data/CHANGELOG.md

@@ -3,6 +3,11 @@
 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.1]
+- fix gemspec
+- fix Docker base build, comment out unneeded broken maven
+- update docs
+
 ## [0.5.0]
 - First good release
 

data/Gemfile.lock

@@ -11,7 +11,7 @@ GIT
 PATH
   remote: .
   specs:
-    jets (0.2.0)
+    jets (0.5.0)
       actionpack
       actionview
       activerecord
@@ -63,7 +63,7 @@ GEM
       tzinfo (~> 1.1)
     arel (9.0.0)
     aws-eventstream (1.0.1)
-    aws-partitions (1.98.0)
+    aws-partitions (1.99.0)
     aws-sdk-cloudformation (1.6.0)
       aws-sdk-core (~> 3)
       aws-sigv4 (~> 1.0)

data/README.md

@@ -9,7 +9,7 @@ Ruby and Lambda splat out a baby and that child's name is Jets.
 
 ## What is Jets?
 
-Jets is a Ruby Serverless Framework that allows you to create applications.  It includes everything required to build an application and deploy it to on AWS Lambda.
+Jets is a Ruby Serverless Framework.  Jets allows you to create serverless applications with a beautiful language: Ruby.  It includes everything required to build an application and deploy it to on AWS Lambda.
 
 It is key to understand AWS Lambda and API Gateway to understand Jets conceptually.  Jets maps your code to Lambda functions and API Gateway resources.
 

data/jets.gemspec

@@ -13,9 +13,11 @@ Gem::Specification.new do |spec|
   spec.homepage      = "https://github.com/tongueroo/jets"
   spec.license       = "MIT"
 
-  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+  vendor_files       = Dir.glob("vendor/**/*")
+  gem_files          = `git ls-files -z`.split("\x0").reject do |f|
     f.match(%r{^(test|spec|features|docs)/})
   end
+  spec.files         = gem_files + vendor_files
   spec.bindir        = "exe"
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})

data/lib/jets/commands/templates/skeleton/config/application.rb.tt

@@ -3,7 +3,7 @@ Jets.application.configure do
   config.api_generator = <%= !!@options[:api] %>
   # config.prewarm.rate = '30 minutes' # default is '30 minutes'
   # config.prewarm.concurrency = 1 # default is 1
-  # config.env_extra = 2 # change also set this with JETS_ENV_EXTRA
+  # config.env_extra = 2 # can also set this with JETS_ENV_EXTRA
   # config.extra_autoload_paths = []
 
   config.function.timeout = 10

data/lib/jets/dotenv.rb

@@ -27,7 +27,7 @@ class Jets::Dotenv
       root.join(".env.#{Jets.env}"),
       root.join(".env.#{Jets.env}.local"),
     ]
-    files << root.join(".env.#{Jets.env}.deploy") if @deploy
+    files << root.join(".env.#{Jets.env}.remote") if @deploy
     files.compact
   end
 

data/lib/jets/internal/app/jobs/jets/preheat_job.rb

@@ -1,4 +1,3 @@
-# Simple initial implementation of a prewarmer
 class Jets::PreheatJob < ApplicationJob
   enabled = Jets.config.prewarm.enabled
   ENABLED = enabled.nil? ? true : enabled # defaults to enabled

data/lib/jets/version.rb

@@ -1,3 +1,3 @@
 module Jets
-  VERSION = "0.5.0"
+  VERSION = "0.5.1"
 end

data/vendor/dynomite/CHANGELOG.md

@@ -0,0 +1,34 @@
+# 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.
+
+## [1.0.7]
+- update DYNOMITE_ENV var
+
+## [1.0.6]
+- rename to dynomite
+
+## [1.0.5]
+- fix jets dynamodb:migrate tip
+
+## [1.0.4]
+- Add and use log method instead of puts to write to stderr by default
+
+## [1.0.3]
+- rename APP_ROOT to JETS_ROOT
+
+## [1.0.2]
+- to_json for json rendering
+
+## [1.0.1]
+- Check dynamodb local is running when configured
+
+## [1.0.0]
+- LSI support
+- automatically infer table_name
+- automatically infer create_table and update_table migrations types
+
+## [0.3.0]
+- DSL methods now available: create_table, update_table
+- Also can add GSI indexes within update_table with: i.gsi

data/vendor/dynomite/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in dynomite.gemspec
+gemspec

data/vendor/dynomite/README.md

@@ -0,0 +1,141 @@
+# Dynomite
+
+A simple wrapper library to make DynamoDB usage a little more friendly.  The modeling is ActiveRecord-ish but not exactly because DynamoDB is a different type of database.  Examples below explain it best:
+
+## Examples
+
+First define a class:
+
+```ruby
+class Post < Dynomite::Item
+  # partition_key "id" # optional, defaults to id
+end
+```
+
+### Create
+
+```ruby
+post = Post.new
+post = post.replace(title: "test title")
+post.attrs # {"id" => "generated-id", title" => "my title"}
+```
+
+`post.attrs[:id]` now contain a generated unique partition_key id.  Usually the partition_key is 'id'. You can set your own unique id also by specifying id.
+
+```ruby
+post = Post.new(id: "myid", title: "my title")
+post.replace
+post.attrs # {"id" => "myid", title" => "my title"}
+```
+
+Note that the replace method replaces the entire item, so you need to merge the attributes if you want to keep the other attributes.  Know this is weird, but this is how DynamoDB works.
+
+### Find
+
+```ruby
+post = Post.find("myid")
+post.attrs = post.attrs.deep_merge("desc": "my desc") # keeps title field
+post.replace
+post.attrs # {"id" => "myid", title" => "my title", desc: "my desc"}
+```
+
+The convenience `attrs` method performs a deep_merge:
+
+```ruby
+post = Post.find("myid")
+post.attrs("desc": "my desc 2") # <= does a deep_merge
+post.replace
+post.attrs # {"id" => "myid", title" => "my title", desc: "my desc 2"}
+```
+
+Note, a race condition edge case can exist when several concurrent replace
+calls are happening.  This is why the interface is called replace to
+emphasis that possibility.
+
+### Delete
+
+```ruby
+resp = Post.delete("myid")  # dynamodb client resp
+# or
+post = Post.find("myid")
+resp = post.delete  # dynamodb client resp
+```
+
+### Scan
+
+```ruby
+options = {}
+posts = Post.scan(options)
+posts # Array of Post items.  [Post.new, Post.new, ...]
+```
+
+### Query
+
+```ruby
+posts = Post.query(
+  index_name: 'category-index',
+  expression_attribute_names: { "#category_name" => "category" },
+  expression_attribute_values: { ":category_value" => "Entertainment" },
+  key_condition_expression: "#category_name = :category_value",
+)
+posts # Array of Post items.  [Post.new, Post.new, ...]
+```
+
+### Where
+
+The where could be prettied up. Appreciate any pull requests.
+
+```ruby
+Post.where({category: "Drama"}, {index_name: "category-index"})
+```
+
+Examples are also in [item_spec.rb](spec/lib/dynomite/item_spec.rb).
+
+## Migration Support
+
+Dynomite supports ActiveRecord-like migrations.  Here's a short example:
+
+```ruby
+class CreateCommentsMigration < Dynomite::Migration
+  def up
+    create_table :comments do |t|
+      t.partition_key "post_id:string" # required
+      t.sort_key  "created_at:string" # optional
+      t.provisioned_throughput(5) # sets both read and write, defaults to 5 when not set
+    end
+  end
+end
+```
+
+More examples are in the [docs/migrations](docs/migrations) folder.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'dynomite'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install dynomite
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/tongueroo/dynomite.
+
+### TODO
+
+* improve Post.where.  Something like `Post.index_name("user_id").where(category_name: "Entertainment")` would be nice.
+* implement `post.update` with `db.update_item` in a Ruby-ish way

data/vendor/dynomite/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/vendor/dynomite/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "dynomite"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/vendor/dynomite/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/vendor/dynomite/docs/migrations/long-example.rb

@@ -0,0 +1,123 @@
+# Note: table name created will be namespaced based on
+# Dynomite::Migration.table_namespace.  This can be set in
+# config/dynamodb.yml
+#
+# development:
+#   table_namespace: "mynamespace"
+#
+# This results in:
+#   create_table "posts"
+# Produces:
+#   table name: "mynamespace-posts"
+#
+# When you're in a in Jets project you can set the namespace based on
+# Jets.config.table_namespace, which is based on the project name and
+# a short version of the environment.  Example:
+#
+# `config/dynamodb.yml`:
+# development:
+#   table_namespace: <%= Jets.config.table_namespace %>
+#
+# If your project_name is demo and environment is production:
+#   create_table "posts" => table name: "demo-prod-posts"
+#
+# If your project_name is proj and environment is staging:
+#   create_table "posts" => table name: "demo-stag-posts"
+#
+# If your project_name is proj and environment is development:
+#   create_table "posts" => table name: "demo-dev-posts"
+#
+# If the table_namespace is set to a blank string or nil, then a namespace
+# will not be prepended at all.
+
+class CreateCommentsMigration < Dynomite::Migration
+  def up
+    create_table :comments do |t|
+      t.partition_key "post_id:string" # required
+      t.sort_key  "created_at:string" # optional
+      t.provisioned_throughput(5) # sets both read and write, defaults to 5 when not set
+
+      # Instead of using partition_key and sort_key you can set the
+      # key schema directly also
+      # t.key_schema([
+      #     {attribute_name: "id", :key_type=>"HASH"},
+      #     {attribute_name: "created_at", :key_type=>"RANGE"}
+      #   ])
+      # t.attribute_definitions([
+      #   {attribute_name: "id", attribute_type: "N"},
+      #   {attribute_name: "created_at", attribute_type: "S"}
+      # ])
+
+      # other ways to set provisioned_throughput
+      # t.provisioned_throughput(:read, 10)
+      # t.provisioned_throughput(:write, 10)
+      # t.provisioned_throughput(
+      #   read_capacity_units: 5,
+      #   write_capacity_units: 5
+      # )
+    end
+  end
+end
+
+class UpdateCommentsMigration < Dynomite::Migration
+  def up
+    update_table :comments do |t|
+
+      # t.global_secondary_index do
+      # t.gsi(METHOD, INDEX_NAME) do
+
+      # You normally create an index like so:
+      #
+      #  t.gsi(:create) do |i|
+      #    i.partition_key = "post_id:string" # partition_key is required
+      #    i.sort_key = "updated_at:string" # sort_key is optional
+      #  end
+      #
+      # The index name will be inferred from the partition_key and sort_key when
+      # not explicitly set.  Examples:
+      #
+      #   index_name = "#{partition_key}-#{sort_key}-index"
+      #   index_name = "post_id-index" # no sort key
+      #   index_name = "post_id-updated_at-index" # has sort key
+      #
+      # The inference allows you to not have to worry about the index
+      # naming scheme. You can still set the index_name explicitly like so:
+      #
+      #  t.gsi(:create, "post_id-updated_at-index") do |i|
+      #    i.partition_key = "post_id:string" # partition_key is required
+      #    i.sort_key = "updated_at:string" # sort_key is optional
+      #  end
+      #
+      t.gsi(:create) do |i|
+        i.partition_key "post_id:string"
+        i.sort_key "updated_at:string" # optional
+
+        # translates to
+        # i.key_schema({...})
+        # also makes sure that the schema_keys are added to the attributes_definitions
+
+        # t.projected_attributes(:all) # default if not called
+        # t.projected_attributes(:keys_only) # other ways to call
+        # t.projected_attributes([:id, :body, :tags, :updated_at])
+        # translates to:
+        # Valid Values: ALL | KEYS_ONLY | INCLUDE
+        # t.projection(
+        #   projection_type: :all, # defaults to all
+        # )
+        # t.projection(
+        #   projection_type: :include, # defaults to all
+        #   non_key_attributes: [:id, :body, :tags, :updated_at], # defaults to all
+        # )
+
+        i.provisioned_throughput(10)
+      end
+
+      t.gsi(:update, "category-index") do |i|
+        i.provisioned_throughput(10)
+      end
+
+      t.gsi(:delete, "category-index")
+    end
+  end
+end
+