lambda_punch 1.0.3 → 1.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 806b9121fb13c00ae8a5e38e39a48cb2f8609aad192f5f3bc32b857032cfd0fa
-  data.tar.gz: 8426e0efa1a7c5f44d79445ea025054f8346f4264983878fc608f91efbcca387
+  metadata.gz: edd0fcb9d2a3d808ef2f2209f7d2b9c344e372fecb918bd6d2e25dfe375b3c55
+  data.tar.gz: 4a0972320ed7f3734e43b9cfe9a9fde1134a2148b44532914361c99bc4b1f4fa
 SHA512:
-  metadata.gz: 0ec52eb4a0f53d3958080a34ed8b5d07e0f0f93e326d1e6e78dad7167ba8c87b5c60074e49d3a7219903d764ff9569b4f94ff3948f5e546e74a380b338025d94
-  data.tar.gz: a8c0b72ccc54367fd683996a0b24d586632e934be647b1f000f8c2bb83e31aac6c14f6c31b539356ae94eb14a55aa06fe9d1698d40a1123336b927fe3e40b164
+  metadata.gz: 07bb2eccf539f0322316520fb0b45ee95110e7e6d47165cc3460542de6629c6f72a616901616fbf93a8fc75fb6fa1208619fcf17e80c059c0f204a21893cc261
+  data.tar.gz: d1414ca50a4bcaca75dd346eab56b360d447f8f7e31736e4fe2a9d62ffafcd79cf9f4f77c5b8b687ce8eba1b3405daa34e06f576aebd64fd5dfe38076fcadd19

data/.devcontainer/Dockerfile

@@ -0,0 +1 @@
+FROM mcr.microsoft.com/devcontainers/ruby:3.1

data/.devcontainer/devcontainer.json

@@ -0,0 +1,19 @@
+{
+  "name": "lambda_punch",
+  "build": {
+    "dockerfile": "Dockerfile"
+  },
+  "features": {
+    "ghcr.io/devcontainers/features/sshd:latest": {}
+  },
+  "customizations": {
+    "vscode": {
+      "settings": {
+        "editor.formatOnSave": true
+      },
+      "extensions": []
+    }
+  },
+  "postCreateCommand": ".devcontainer/postCreate.sh",
+  "remoteUser": "vscode"
+}

data/.devcontainer/postCreate.sh

@@ -0,0 +1,6 @@
+#!/bin/sh
+set -e
+
+sudo rm -rf /opt
+sudo mkdir /opt
+sudo chown -R $USER /opt

data/.github/workflows/test.yml

@@ -2,16 +2,15 @@ name: Test
 on: [push]
 jobs:
   test:
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-20.04
     steps:
       - name: Checkout
-        uses: actions/checkout@v2
-      - name: Bootstrap
-        run: |
-          ./bin/bootstrap
-      - name: Setup
-        run: |
-          ./bin/setup
-      - name: Test
-        run: |
-          ./bin/test
+        uses: actions/checkout@v3
+      - name: Setup & Test
+        uses: devcontainers/ci@v0.3
+        with:
+          env: |
+            CI
+          runCmd: |
+            ./bin/setup
+            ./bin/test

data/CHANGELOG.md

@@ -1,8 +1,20 @@
+## [1.1.1] - 2023-04-16
+
+### Fixed
+
+- The `lambda_punch` install file.
+
+## [1.1.0] - 2023-04-16
+
+### Added
+
+- New `lambda_punch` install interface.
+
 ## [1.0.3] - 2021-10-27
 
 ### Added
 
--
+- Any Timeout Gem. Tempfile Location Interface 
 
 ### Changed
 

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    lambda_punch (1.0.3)
+    lambda_punch (1.1.1)
       concurrent-ruby
       rake
       rb-inotify
@@ -74,7 +74,7 @@ GEM
     concurrent-ruby (1.1.9)
     crass (1.0.6)
     erubi (1.10.0)
-    ffi (1.15.4)
+    ffi (1.15.5)
     globalid (0.5.2)
       activesupport (>= 5.0)
     i18n (1.8.10)
@@ -87,11 +87,13 @@ GEM
     marcel (1.0.2)
     method_source (1.0.0)
     mini_mime (1.1.2)
+    mini_portile2 (2.6.1)
     minitest (5.14.4)
     minitest-focus (1.3.1)
       minitest (>= 4, < 6)
     nio4r (2.5.8)
-    nokogiri (1.12.5-x86_64-linux)
+    nokogiri (1.12.5)
+      mini_portile2 (~> 2.6.1)
       racc (~> 1.4)
     pry (0.14.1)
       coderay (~> 1.1)
@@ -137,7 +139,7 @@ GEM
       activesupport (>= 4.0)
       sprockets (>= 3.0.0)
     thor (1.1.0)
-    timeout (0.2.0)
+    timeout (0.3.2)
     tzinfo (2.0.4)
       concurrent-ruby (~> 1.0)
     websocket-driver (0.7.5)
@@ -146,6 +148,8 @@ GEM
     zeitwerk (2.5.1)
 
 PLATFORMS
+  aarch64-linux
+  arm64-darwin-22
   x86_64-linux
 
 DEPENDENCIES

data/README.md

@@ -4,7 +4,7 @@
 
 # 👊 LambdaPunch
 
-<a href="https://lamby.custominktech.com"><img src="https://user-images.githubusercontent.com/2381/59363668-89edeb80-8d03-11e9-9985-2ce14361b7e3.png" alt="Lamby: Simple Rails & AWS Lambda Integration using Rack." align="right" width="300" /></a>Asynchronous background job processing for AWS Lambda with Ruby using [Lambda Extensions](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html). Inspired by the [SuckerPunch](https://github.com/brandonhilkert/sucker_punch) gem but specifically tooled to work with Lambda's invoke model.
+<a href="https://lamby.custominktech.com"><img src="https://raw.githubusercontent.com/customink/lamby/master/images/social2.png" alt="Lamby: Simple Rails & AWS Lambda Integration using Rack." align="right" width="450" style="margin-left:1rem;margin-bottom:1rem;" /></a>Asynchronous background job processing for AWS Lambda with Ruby using [Lambda Extensions](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-extensions-api.html). Inspired by the [SuckerPunch](https://github.com/brandonhilkert/sucker_punch) gem but specifically tooled to work with Lambda's invoke model.
 
 **For a more robust background job solution, please consider using AWS SQS with the [Lambdakiq](https://github.com/customink/lambdakiq) gem. A drop-in replacement for [Sidekiq](https://github.com/mperham/sidekiq) when running Rails in AWS Lambda using the [Lamby](https://lamby.custominktech.com/) gem.**
 
@@ -18,35 +18,36 @@ The LambdaPunch extension process is very small and lean. It only requires a few
 
 ## 🎁 Installation
 
-Add this line to your project's `Gemfile` and then make sure to `bundle install` afterward.
+Add this line to your project's `Gemfile` and then make sure to `bundle install` afterward. It is only needed in the `production` group.
 
 ```ruby
 gem 'lambda_punch'
 ```
 
-Now, within your application's handler file, make sure to start the LambdaPunch DRb server outside of your handler method. Within the handler method, add an `ensure` section that lets the extension process know the request is done.
+Within your project or [Rails application's](https://lamby.custominktech.com/docs/anatomy) `Dockerfile`, add the following. Make sure you do this before you `COPY` your code. The idea is to implicitly use the default `USER root` since it needs permissions to create an `/opt/extensions` directory.
 
-```ruby
-LambdaPunch.start_server!
-
-def handler(event:, context:)
-  # ...
-ensure
-  LambdaPunch.handled!(context)
-end
+```dockerfile
+RUN gem install lambda_punch && lambda_punch install
 ```
 
-Within your project or [Rails application's](https://lamby.custominktech.com/docs/anatomy) `Dockerfile`, after you copy your code, add this `RUN` command to install the extension within your container's `/opt/extensions` directory.
+Installation with AWS Lambda via the [Lamby](https://lamby.custominktech.com/) v4 (or higher) gem can be done using Lamby's `handled_proc` config. For example, appends these to your `config/environments/production.rb` file. Here we are ensuring that the LambdaPunch DRb server is running and that after each Lamby request we notify LambdaPunch.
 
-```dockerfile
-RUN bundle exec rake lambda_punch:install
+```ruby
+config.to_prepare { LambdaPunch.start_server! }
+config.lamby.handled_proc = Proc.new do |_event, context|
+  LambdaPunch.handled!(context)
+end
 ```
 
-If you are using `LambdaPunch` with a non-Rails project, add this to your Rake file
+If you are using an older version of Lamby or a simple Ruby project with your own handler method, the installation would look something like this:
 
 ```ruby
-spec = Gem::Specification.find_by_name 'lambda_punch'
-load "#{spec.gem_dir}/lib/lambda_punch/tasks/install.rake"
+LambdaPunch.start_server!
+def handler(event:, context:)
+  # ...
+ensure
+  LambdaPunch.handled!(context)
+end
 ```
 
 ## 🧰 Usage
@@ -59,12 +60,11 @@ LambdaPunch.push do
 end
 ```
 
-For example, if you are using Rails with AWS Lambda via the [Lamby](https://lamby.custominktech.com/) gem along with [New Relic APM](https://dev.to/aws-heroes/using-new-relic-apm-with-rails-on-aws-lambda-51gi) here is how your handler function might appear to ensure their metrics are flushed after each request.
+A common use case would be to ensure the [New Relic APM](https://dev.to/aws-heroes/using-new-relic-apm-with-rails-on-aws-lambda-51gi) flushes its data after each request. Using Lamby in your `config/environments/production.rb`  file would look like this:
 
 ```ruby
-def handler(event:, context:)
-  Lamby.handler $app, event, context
-ensure
+config.to_prepare { LambdaPunch.start_server! }
+config.lamby.handled_proc = Proc.new do |_event, context|
   LambdaPunch.push { NewRelic::Agent.agent.flush_pipe_data }
   LambdaPunch.handled!(context)
 end

data/bin/setup

@@ -1,6 +1,6 @@
 #!/bin/sh
 set -e
 
-docker-compose run \
-  lambdapunch \
-  ./bin/_setup
+echo '== Installing dependencies =='
+bundle config set --local path 'vendor/bundle'
+bundle install

data/bin/test

@@ -1,6 +1,4 @@
 #!/bin/sh
 set -e
 
-docker-compose run \
-  lambdapunch \
-  ./bin/_test
+bundle exec rake test

data/exe/lambda_punch

@@ -0,0 +1,11 @@
+#!/usr/bin/env ruby
+
+require 'rubygems'
+require 'rake'
+
+spec = Gem::Specification.find_by_name 'lambda_punch'
+load "#{spec.gem_dir}/lib/lambda_punch/tasks/install.rake"
+
+command = ARGV[0] || 'install'
+
+Rake::Task["lambda_punch:#{command}"].invoke

data/lib/lambda_punch/version.rb

@@ -1,3 +1,3 @@
 module LambdaPunch
-  VERSION = "1.0.3"
+  VERSION = "1.1.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: lambda_punch
 version: !ruby/object:Gem::Version
-  version: 1.0.3
+  version: 1.1.1
 platform: ruby
 authors:
 - Ken Collins
-autorequire: 
+autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-10-28 00:00:00.000000000 Z
+date: 2023-04-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: concurrent-ruby
@@ -111,28 +111,27 @@ dependencies:
 description: 'LambdaPunch: Async Processing using Lambda Extensions'
 email:
 - ken@metaskills.net
-executables: []
+executables:
+- lambda_punch
 extensions: []
 extra_rdoc_files: []
 files:
+- ".devcontainer/Dockerfile"
+- ".devcontainer/devcontainer.json"
+- ".devcontainer/postCreate.sh"
 - ".github/workflows/test.yml"
 - ".gitignore"
 - CHANGELOG.md
 - CODE_OF_CONDUCT.md
-- Dockerfile
 - Gemfile
 - Gemfile.lock
 - LICENSE.txt
 - README.md
 - Rakefile
-- bin/_setup
-- bin/_test
-- bin/bootstrap
 - bin/console
-- bin/run
 - bin/setup
 - bin/test
-- docker-compose.yml
+- exe/lambda_punch
 - lambda_punch.gemspec
 - lib/lambda_punch.rb
 - lib/lambda_punch/api.rb
@@ -154,7 +153,7 @@ metadata:
   homepage_uri: https://github.com/customink/lambda_punch
   source_code_uri: https://github.com/customink/lambda_punch
   changelog_uri: https://github.com/customink/lambda_punch/blob/main/CHANGELOG.md
-post_install_message: 
+post_install_message:
 rdoc_options: []
 require_paths:
 - lib
@@ -169,8 +168,8 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
-signing_key: 
+rubygems_version: 3.4.7
+signing_key:
 specification_version: 4
 summary: 'LambdaPunch: Async Processing using Lambda Extensions'
 test_files: []

data/Dockerfile

@@ -1,2 +0,0 @@
-FROM public.ecr.aws/sam/build-ruby2.7
-WORKDIR /var/task

data/bin/_setup

@@ -1,6 +0,0 @@
-#!/bin/sh
-set -e
-
-echo '== Installing dependencies =='
-bundle config set --local path 'vendor/bundle'
-bundle install

data/bin/_test

@@ -1,4 +0,0 @@
-#!/bin/sh
-set -e
-
-bundle exec rake test

data/bin/bootstrap

@@ -1,6 +0,0 @@
-#!/bin/sh
-set -e
-
-echo '== Building containers =='
-docker pull public.ecr.aws/sam/build-ruby2.7
-docker-compose build 

data/bin/run

@@ -1,6 +0,0 @@
-#!/bin/sh
-set -e
-
-docker-compose run \
-  lambdapunch \
-  $@

data/docker-compose.yml

@@ -1,10 +0,0 @@
-version: '3.7'
-services:
-  lambdapunch:
-    build:
-      context: .
-      dockerfile: Dockerfile
-    environment:
-      - CI=${CI}
-    volumes:
-      - ${PWD}:/var/task:delegated