jets 0.8.18 → 0.9.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 23fe5d6d20d288bc4f2b791da60476662930ab3047a55d9e1904d168a875743c
-  data.tar.gz: 0f1c04626989dbb8bb9393f3c67e94aedc7da3605102715df25b2ad282bcba35
+  metadata.gz: a34b4cffc9a96f0d4ce4821f38be3fef03a84a5dfa779a0ce4574b7c41fd8212
+  data.tar.gz: 77e840eb549a58d91c9899b79b0104f9d33e903fa4c1d53b171a168b0416fc64
 SHA512:
-  metadata.gz: dd410110fe51ea01517dbe324b274f4ec883ab99640603c340f000ca5a6d2b1e6e2c7dedfd0710ebc9a10611398d21d4072634a16a627dd6fa4cdb1aede4f2fc
-  data.tar.gz: 3c5e482eff4de95d39ac0bd70a6aab3316b938d4b2f0c62e9ee695d5b899c4d18d0df7505bc544367092ae98899234d0e904b88ca79069dc9bd9af2587301b35
+  metadata.gz: 0bbf43c980eef26615b9eb8c4167c578da79c3cdf5af17d866e1fd7276618c593997f51e7a31316c96d1f561a27fb3d829ad1ea4e2b5a5f77fd2f6b7cbf906f5
+  data.tar.gz: 9cca888aaca0c205722c93858aad544ace8d8fe71255806a373d18461744070e5105ef055e63e1d27a4d3683a2d509063ac78403cb33ef54b869e44d0c5ec112

data/.gitmodules

@@ -1,6 +1,3 @@
-[submodule "spec/fixtures/apps/demo"]
-	path = spec/fixtures/apps/demo
-	url = https://github.com/tongueroo/demo.git
 [submodule "vendor/lambdagem"]
 	path = vendor/lambdagem
 	url = https://github.com/tongueroo/lambdagem.git

data/CHANGELOG.md

@@ -3,8 +3,27 @@
 All notable changes to this project will be documented in this file.
 This project *loosely tries* to adhere to [Semantic Versioning](http://semver.org/), even before v1.0.
 
+## [0.9.0]
+- Remove class name from the namespace. So namespace only has method name now. NOTE: This means upgrading from 0.8.x to 0.9.x requires a blue-green update.
+- Add upgrading docs.
+- Stack DSL: To support the concept of Custom Shared Resources. Supports extensions and simple functions also.
+- Stack DSL: Allow for control of DependsOn attribute.
+- Stack DSL: `MyStack.lookup` method
+- Associated resource extensions support
+- Associated resources multiple form support: long, medium, short
+- Add `jets new --mode`: 3 modes: html, api, job. Remove the `--api`
+- IAM policies inherit from higher precedence and superclasses.
+- Add `jets runner` command
+- Fix AWS Config Rules support
+- Rename event_rule to events_rule
+- Remove submodule project demo fixture in favor of spec/fixtures/apps/franky
+- Add spec/bin/integration.sh - Simpler than the CI one and more immediately useful
+- Improve AWS Config Rules docs
+- Add config rules namespace setting
+- Custom inflections support
+
 ## [0.8.18]
-- improve performance of Jets.aws.region
+- improve performance of Jets.aws.region, pull request #40 from tongueroo/dir-glob
 
 ## [0.8.17]
 - fix Jets.eager_load

data/Gemfile.lock

@@ -11,7 +11,7 @@ GIT
 PATH
   remote: .
   specs:
-    jets (0.8.18)
+    jets (0.9.0)
       actionpack (>= 5.2.1)
       actionview (>= 5.2.1)
       activerecord (>= 5.2.1)
@@ -21,6 +21,7 @@ PATH
       aws-sdk-dynamodb
       aws-sdk-lambda
       aws-sdk-s3
+      aws-sdk-sns
       colorize
       dotenv
       gems
@@ -89,6 +90,9 @@ GEM
       aws-sdk-core (~> 3, >= 3.26.0)
       aws-sdk-kms (~> 1)
       aws-sigv4 (~> 1.0)
+    aws-sdk-sns (1.5.0)
+      aws-sdk-core (~> 3, >= 3.26.0)
+      aws-sigv4 (~> 1.0)
     aws-sigv4 (1.0.3)
     builder (3.2.3)
     byebug (10.0.2)
@@ -170,4 +174,4 @@ DEPENDENCIES
   webpacker!
 
 BUNDLED WITH
-   1.16.4
+   1.16.3

data/README/prerelease.md

@@ -0,0 +1,6 @@
+# Prerelease Checklist
+
+This is a pre-release checklist for major and minor version bumps.
+
+* Run Through tests in: [testing.md](testing.md)
+* Deploy CRUD app to AWS Lambda and verify it works

data/README/testing.md

@@ -0,0 +1,41 @@
+# Testing
+
+## Unit
+
+To run unit tests:
+
+    bundle exec rspec
+
+## Integration
+
+### Locally
+
+To run the integration tests locally, you need to create a new Jets CRUD project and start the server:
+
+    jets new demo
+    cd demo
+    jets generate scaffold Post title:string
+    jets server
+
+Then you can run the postman tests:
+
+    spec/integration/local.sh
+
+The integration_local.sh script ensures that the necessary data exists for the postman integration test to pass.  It ultimately calls:
+
+    newman run spec/integration/fixtures/postman/collection.json -e spec/integration/fixtures/postman/environment.json
+
+The integration test results should look something like this:
+
+* [Jets Integration Test Results](https://gist.github.com/tongueroo/fcea2b2f48342d1448d3f258fcd6536c)
+
+### Remotely
+
+Then you can deploy the jets app and test it on real AWS Lambda.
+
+    cp ~/environment/.env.development.remote . # assumes you have a .env.development.remote
+    jets deploy
+
+Run the remote integration script:
+
+    spec/integration/remote.sh

data/Rakefile

@@ -5,6 +5,13 @@ task :default => :spec
 
 RSpec::Core::RakeTask.new
 
+namespace :spec do
+  desc "Run integration test"
+  task :integration do
+    system("spec/bin/integration.sh")
+  end
+end
+
 require_relative "lib/jets"
 desc "Generates cli reference docs as markdown"
 task :docs do
@@ -17,4 +24,5 @@ require 'jets/rdoc'
 
 RDoc::Task.new do |rdoc|
   rdoc.options += Jets::Rdoc.options
-end
+end
+

data/jets.gemspec

@@ -36,6 +36,7 @@ Gem::Specification.new do |spec|
   spec.add_dependency "aws-sdk-dynamodb"
   spec.add_dependency "aws-sdk-lambda"
   spec.add_dependency "aws-sdk-s3"
+  spec.add_dependency "aws-sdk-sns"
   spec.add_dependency "colorize"
   spec.add_dependency "dotenv"
   spec.add_dependency "hashie"

data/lib/jets.rb

@@ -11,43 +11,42 @@ module Jets
   # When we update Jets::RUBY_VERSION, need to update lambdagem/base.rb: def jets_ruby_version also
   RUBY_VERSION = "2.5.0"
 
-  autoload :CLI, "jets/cli"
-  autoload :Commands, "jets/commands"
-
+  autoload :Application, "jets/application"
   autoload :AwsInfo, "jets/aws_info"
   autoload :AwsServices, "jets/aws_services"
+  autoload :Booter, 'jets/booter'
   autoload :Builders, 'jets/builders'
   autoload :Call, "jets/call"
   autoload :Cfn, 'jets/cfn'
+  autoload :CLI, "jets/cli"
+  autoload :Commands, "jets/commands"
   autoload :Controller, 'jets/controller'
+  autoload :Core, "jets/core"
+  autoload :Dotenv, 'jets/dotenv'
   autoload :Erb, "jets/erb"
   autoload :Generator, "jets/generator"
+  autoload :IO, "jets/io"
   autoload :Job, 'jets/job'
+  autoload :Klass, 'jets/klass'
   autoload :Lambda, 'jets/lambda'
+  autoload :Logger, "jets/logger"
   autoload :Naming, 'jets/naming'
   autoload :PolyFun, 'jets/poly_fun'
+  autoload :Preheat, "jets/preheat"
   autoload :Processors, 'jets/processors'
+  autoload :Rdoc, "jets/rdoc"
+  autoload :Resource, "jets/resource"
   autoload :Route, "jets/route"
   autoload :Router, "jets/router"
+  autoload :RubyServer, "jets/ruby_server"
   autoload :Rule, 'jets/rule'
   autoload :Server, "jets/server"
-
-  autoload :Application, "jets/application"
-  autoload :Booter, 'jets/booter'
-  autoload :Core, "jets/core"
-  autoload :Dotenv, 'jets/dotenv'
-  autoload :Klass, 'jets/klass'
-  autoload :Util, "jets/util"
+  autoload :Stack, "jets/stack"
   autoload :Timing, "jets/timing"
-  autoload :Preheat, "jets/preheat"
-  extend Core # root, logger, etc
-
-  autoload :RubyServer, "jets/ruby_server"
-  autoload :IO, "jets/io"
-  autoload :Logger, "jets/logger"
+  autoload :Util, "jets/util"
+  autoload :Inflections, "jets/inflections"
 
-  autoload :Resource, "jets/resource"
-  autoload :Rdoc, "jets/rdoc"
+  extend Core # root, logger, etc
 end
 
 require "jets/core_ext/kernel"

data/lib/jets/application.rb

@@ -11,11 +11,16 @@ class Jets::Application
   end
 
   def setup!
+    load_inflections
     load_configs # load config object so following methods can use it
     setup_auto_load_paths
     load_routes
   end
 
+  def load_inflections
+    Jets::Inflections.load!
+  end
+
   def config
     config = ActiveSupport::OrderedOptions.new
 
@@ -30,6 +35,9 @@ class Jets::Application
       'https://gems.lambdagems.com'
     ]
 
+    config.inflections = ActiveSupport::OrderedOptions.new
+    config.inflections.irregular = {}
+
     config
   end
   memoize :config
@@ -91,12 +99,27 @@ class Jets::Application
 
     # Must set default iam_policy here instead of `def config` because we need access to
     # the project_namespace and if we call it from `def config` we get an infinit loop
-    config.iam_policy ||= [{
-      sid: "Statement1",
+    config.iam_policy ||= default_iam_policy(project_namespace)
+    config.managed_policy_definitions ||= [] # default empty
+  end
+
+  def default_iam_policy(project_namespace)
+    logs = {
       action: ["logs:*"],
       effect: "Allow",
       resource: "arn:aws:logs:#{Jets.aws.region}:#{Jets.aws.account}:log-group:/aws/lambda/#{project_namespace}-*",
-    }]
+    }
+    policies = [logs]
+
+    if Jets::Stack.has_resources?
+      cloudformation = {
+        action: ["cloudformation:DescribeStacks"],
+        effect: "Allow",
+        resource: "arn:aws:cloudformation:#{Jets.aws.region}:#{Jets.aws.account}:stack/#{project_namespace}*",
+      }
+      policies << cloudformation
+    end
+    policies
   end
 
   # It is pretty easy to attempt to set environment variables without

data/lib/jets/aws_services.rb

@@ -1,81 +1,48 @@
-require "aws-sdk-s3"
 require "aws-sdk-cloudformation"
 require "aws-sdk-cloudwatchlogs"
 require "aws-sdk-lambda"
+require "aws-sdk-s3"
 require "aws-sdk-sts"
+# Not used in Jets internally but convenient for shared resources
+require "aws-sdk-sns"
 
 module Jets::AwsServices
-  def s3
-    @s3 ||= Aws::S3::Client.new
-  end
+  autoload :StackStatus, 'jets/aws_services/stack_status'
+  include StackStatus
+  extend Memoist
 
-  def s3_resource
-    @s3_resource ||= Aws::S3::Resource.new
+  def cfn
+    Aws::CloudFormation::Client.new
   end
+  memoize :cfn
 
-  def cfn
-    @cfn ||= Aws::CloudFormation::Client.new
+  def logs
+    Aws::CloudWatchLogs::Client.new
   end
+  memoize :logs
 
   def lambda
-    @lambda ||= Aws::Lambda::Client.new
+    Aws::Lambda::Client.new
   end
+  memoize :lambda
 
-  def sts
-    @sts ||= Aws::STS::Client.new
+  def s3
+    Aws::S3::Client.new
   end
+  memoize :s3
 
-  def logs
-    @logs ||= Aws::CloudWatchLogs::Client.new
+  def s3_resource
+    Aws::S3::Resource.new
   end
+  memoize :s3_resource
 
-  def stack_exists?(stack_name)
-    return false if ENV['TEST']
-
-    exist = nil
-    begin
-      # When the stack does not exist an exception is raised. Example:
-      # Aws::CloudFormation::Errors::ValidationError: Stack with id blah does not exist
-      resp = cfn.describe_stacks(stack_name: stack_name)
-      exist = true
-    rescue Aws::CloudFormation::Errors::ValidationError => e
-      if e.message =~ /does not exist/
-        exist = false
-      elsif e.message.include?("'stackName' failed to satisfy constraint")
-        # Example of e.message when describe_stack with invalid stack name
-        # "1 validation error detected: Value 'instance_and_route53' at 'stackName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z][-a-zA-Z0-9]*|arn:[-a-zA-Z0-9:/._+]*"
-        puts "Invalid stack name: #{stack_name}"
-        puts "Full error message: #{e.message}"
-        exit 1
-      else
-        raise # re-raise exception  because unsure what other errors can happen
-      end
-    end
-    exist
+  def sts
+    Aws::STS::Client.new
   end
+  memoize :sts
 
-  # All CloudFormation states listed here: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-describing-stacks.html
-  #
-  # Returns resp so we can use it to grab data about the stack without calling api again.
-  def stack_in_progress?(stack_name)
-    return true if !stack_exists?(stack_name)
-
-    # Assumes stack exists
-    resp = cfn.describe_stacks(stack_name: stack_name)
-    status = resp.stacks[0].stack_status
-    if status =~ /_IN_PROGRESS$/
-      puts "The '#{stack_name}' stack status is #{status}. " \
-           "Please wait until the stack is ready and try again.".colorize(:red)
-      exit 0
-    elsif resp.stacks[0].outputs.empty? && status != 'ROLLBACK_COMPLETE'
-      # This Happens when the miminal stack fails at the very beginning.
-      # There is no s3 bucket at all.  User should delete the stack.
-      puts "The minimal stack failed to create. Please delete the stack first and try again. " \
-      "You can delete the CloudFormation stack or use the `jets delete` command"
-      exit 0
-    else
-      true
-    end
+  def sns
+    Aws::SNS::Client.new
   end
-
+  memoize :sns
 end

data/lib/jets/aws_services/stack_status.rb

@@ -0,0 +1,52 @@
+module Jets::AwsServices
+  module StackStatus
+    def stack_exists?(stack_name)
+      return false if ENV['TEST']
+
+      exist = nil
+      begin
+        # When the stack does not exist an exception is raised. Example:
+        # Aws::CloudFormation::Errors::ValidationError: Stack with id blah does not exist
+        resp = cfn.describe_stacks(stack_name: stack_name)
+        exist = true
+      rescue Aws::CloudFormation::Errors::ValidationError => e
+        if e.message =~ /does not exist/
+          exist = false
+        elsif e.message.include?("'stackName' failed to satisfy constraint")
+          # Example of e.message when describe_stack with invalid stack name
+          # "1 validation error detected: Value 'instance_and_route53' at 'stackName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z][-a-zA-Z0-9]*|arn:[-a-zA-Z0-9:/._+]*"
+          puts "Invalid stack name: #{stack_name}"
+          puts "Full error message: #{e.message}"
+          exit 1
+        else
+          raise # re-raise exception  because unsure what other errors can happen
+        end
+      end
+      exist
+    end
+
+    # All CloudFormation states listed here: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-describing-stacks.html
+    #
+    # Returns resp so we can use it to grab data about the stack without calling api again.
+    def stack_in_progress?(stack_name)
+      return true if !stack_exists?(stack_name)
+
+      # Assumes stack exists
+      resp = cfn.describe_stacks(stack_name: stack_name)
+      status = resp.stacks[0].stack_status
+      if status =~ /_IN_PROGRESS$/
+        puts "The '#{stack_name}' stack status is #{status}. " \
+             "Please wait until the stack is ready and try again.".colorize(:red)
+        exit 0
+      elsif resp.stacks[0].outputs.empty? && status != 'ROLLBACK_COMPLETE'
+        # This Happens when the miminal stack fails at the very beginning.
+        # There is no s3 bucket at all.  User should delete the stack.
+        puts "The minimal stack failed to create. Please delete the stack first and try again. " \
+        "You can delete the CloudFormation stack or use the `jets delete` command"
+        exit 0
+      else
+        true
+      end
+    end
+  end
+end

data/lib/jets/builders.rb

@@ -1,6 +1,7 @@
 class Jets::Builders
-  autoload :Deducer, "jets/builders/deducer"
-  autoload :HandlerGenerator, "jets/builders/handler_generator"
   autoload :CodeBuilder, "jets/builders/code_builder"
+  autoload :Deducer, "jets/builders/deducer"
   autoload :GemReplacer, "jets/builders/gem_replacer"
+  autoload :HandlerGenerator, "jets/builders/handler_generator"
+  autoload :SharedDeducer, "jets/builders/shared_deducer"
 end