yake 0.4.1 → 0.4.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 6bd208d64f868cf763f2cb19ff4b766a771a3011b6edda1918cf4e3f9436b1c0
-  data.tar.gz: 439c99ae77a312ad882f8d5b58061dd9841e7f163a6e01476a54845ad38efab5
+  metadata.gz: 224ba56816d47b87e5691c7d95904807b9754b6df437fa85a23e8c3190534c8c
+  data.tar.gz: de423580d089fd5879788cd6491daeb30012adcdc9ae7ff6d666a090e8bf73a8
 SHA512:
-  metadata.gz: 2052948f82b026240655aaf07d6a5a15dc687aa432d97fdcbec0b9c4cb88aca4c64f50d7051336f1a7b99d005b2f9d6234f50a750221897d86a6d033012200e6
-  data.tar.gz: 8800efb2e6428321aadc94c84788f8918290ab620476f51e20d1e0cfd66170bd4a3002ff86c5d4554de5c3aceaa81ecefb14fcb393fe0f5ac368d70233a83429
+  metadata.gz: d270d5b7eb530917d3d7f2e0ddd2e847fd40300215366f22aa4dd67808f84c028172be6e3f8c9a2894a192a527cbbb361c2ab346b17e4b90ec02ec72d8865fa1
+  data.tar.gz: 23120b48ee291d9698b83cad68f4d54ebc5abbb99ba72ed3f01af1d3f36a4a7ac72f20e5b468e290c9ed7995d3a9d541e9f07b2d52e254afd716317f3b9794d4

data/README.md

@@ -9,7 +9,7 @@ Write your AWS Lambda function handlers using a Rake-like declarative syntax:
 
 ```ruby
 # ./lambda_function.rb
-require "yake"
+require 'yake'
 
 handler :lambda_handler do |event|
   # Your code here
@@ -22,11 +22,11 @@ You can even declare Sinatra-like API Gateway routes for a main entrypoint:
 
 ```ruby
 # ./lambda_function.rb
-require "yake/api"
+require 'yake/api'
 
-header "content-type" => "application/json"
+header 'content-type' => 'application/json'
 
-get "/fizz" do
+get '/fizz' do
   respond 200, { ok: true }.to_json
 end
 
@@ -44,7 +44,7 @@ end
 Add this line to your application's Gemfile:
 
 ```ruby
-gem "yake"
+gem 'yake'
 ```
 
 And then execute:
@@ -82,10 +82,12 @@ REPORT RequestId: 149c500f-028a-4b57-8977-0ef568cf8caf	Duration: 43.97 ms	Billed
 
 Logging the request ID in this way makes gathering logs lines for a particular execution in CloudWatch much easier.
 
-This feature can be disabled by adding a declaration in your handler file:
+You can or disable the logger:
 
 ```ruby
-logging :off
+logging :off              # disables logging entirely
+logging pretty: false     # Logs event/result in compact JSON
+logging :on, MyLogger.new # Use a custom logger
 ```
 
 Include `Yake::Logger` on a class to access this logger:
@@ -108,35 +110,35 @@ Requiring the `yake/api` module will add the API-specific DSL into your handler.
 Define API routes using Sinatra-like syntax
 
 ```ruby
-any "/…" do |event|
+any '/…' do |event|
   # Handle 'ANY /…' route key events
 end
 
-delete "/…" do |event|
+delete '/…' do |event|
   # Handle 'DELETE /…' route key events
 end
 
-get "/…" do |event|
+get '/…' do |event|
   # Handle 'GET /…' route key events
 end
 
-head "/…" do |event|
+head '/…' do |event|
   # Handle 'HEAD /…' route key events
 end
 
-options "/…" do |event|
+options '/…' do |event|
   # Handle 'OPTIONS /…' route key events
 end
 
-patch "/…" do |event|
+patch '/…' do |event|
   # Handle 'PATCH /…' route key events
 end
 
-post "/…" do |event|
+post '/…' do |event|
   # Handle 'POST /…' route key events
 end
 
-put "/…" do |event|
+put '/…' do |event|
   # Handle 'PUT /…' route key events
 end
 ```
@@ -146,14 +148,14 @@ Helper methods are also made available to help produce a response for API Gatewa
 Set a default header for ALL responses:
 
 ```ruby
-header "content-type" => "application/json; charset=utf-8"
-header "x-custom-header" => "fizz"
+header 'content-type' => 'application/json; charset=utf-8'
+header 'x-custom-header' => 'fizz'
 ```
 
 Produce an API Gateway-style response object:
 
 ```ruby
-respond 200, { ok: true }.to_json, "x-extra-header" => "buzz"
+respond 200, { ok: true }.to_json, 'x-extra-header' => 'buzz'
 # {
 #   "statusCode" => 200,
 #   "body" => '{"ok":true}',
@@ -177,11 +179,35 @@ end
 
 Finally, `yake` does not depend on any other gems, using the Ruby stdlib only. This helps keep your Lambda packages slim & speedy.
 
-## Development
+## Datadog Integration
+
+As of `~> 0.4`, `yake` comes with a helper for writing Lambdas that integrate with Datadog's `datadog-ruby` gem.
 
-After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+Creating a Lambda handler that wraps the Datadog tooling is easy:
+
+```ruby
+require 'aws-sdk-someservice'
+require 'yake/datadog'
+
+# Configure Datadog to use AWS tracing
+Datadog::Lambda.configure_apm { |config| config.use :aws }
+
+datadog :handler do |event|
+  # …
+end
+```
+
+## Deployment
+
+After writing your Lambda handler code you can deploy it to AWS using any number of tools. I recommend the following tools:
+
+- [Terraform](https://www.terraform.io) — my personal favorite Infrastructure-as-Code tool
+- [AWS SAM](https://aws.amazon.com/serverless/sam/) — a great alternative with less configuration than Terraform
+- [Serverless](https://www.serverless.com) — Supposedly the most popular option, though I have not used it
+
+## Development
 
-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 the created tag, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+After checking out the repo, run `bundle` to install dependencies. Then, run `rake spec` to run the tests.
 
 ## Contributing
 

data/lib/yake/dsl.rb

@@ -22,7 +22,8 @@ module Yake
 
     ##
     # Turn logging on/off
-    def logging(switch, logger = nil)
+    def logging(switch = :on, logger = nil, pretty: true)
+      Yake.pretty = pretty
       if switch == :on
         Yake.logger = logger
       elsif switch == :off

data/lib/yake/logger.rb

@@ -5,7 +5,7 @@ require 'logger'
 
 module Yake
   module Logger
-    attr_accessor :logger
+    attr_writer :logger
 
     def logger
       @logger ||= Yake.logger
@@ -27,17 +27,24 @@ module Yake
   end
 
   class << self
-    attr_accessor :logger
+    attr_writer :logger, :pretty
 
     def logger
       @logger ||= Logger.new
     end
 
+    def pretty?
+      @pretty != false
+    end
+
     def wrap(event = nil, context = nil, &block)
       original_progname = logger.progname
-      logger.progname = context&.aws_request_id
-      logger.info("EVENT #{ event.to_json }")
-      yield(event, context).tap { |res| logger.info("RETURN #{ res.to_json }") }
+      logger.progname   = context&.aws_request_id
+      jsonify           = -> (obj) { pretty? ? JSON.pretty_generate(obj) : obj.to_json }
+      logger.info("EVENT #{ jsonify === event }")
+      yield(event, context).tap do |res|
+        logger.info("RETURN #{ jsonify === res }")
+      end
     ensure
       logger.progname = original_progname
     end

data/lib/yake/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Yake
-  VERSION = '0.4.1'
+  VERSION = '0.4.2'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: yake
 version: !ruby/object:Gem::Version
-  version: 0.4.1
+  version: 0.4.2
 platform: ruby
 authors:
 - Alexander Mancevice
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-10-15 00:00:00.000000000 Z
+date: 2021-11-04 00:00:00.000000000 Z
 dependencies: []
 description:
 email:
@@ -18,7 +18,6 @@ extensions: []
 extra_rdoc_files: []
 files:
 - LICENSE
-- LICENSE.txt
 - README.md
 - lib/yake.rb
 - lib/yake/api.rb

data/LICENSE.txt

@@ -1,21 +0,0 @@
-The MIT License (MIT)
-
-Copyright (c) 2021 Alexander Mancevice
-
-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.