Refactor to multiple python versions & test integration

Author: kilna-magento

Dockerfile

@@ -0,0 +1,6 @@
+FROM python:2.7-alpine
+LABEL maintainer="Kilna kilna@kilna.com"
+RUN pip install python-lambda &&\
+    mkdir /lambda
+COPY bin/* /usr/local/bin/
+WORKDIR /lambda

Dockerfile-2.7

@@ -0,0 +1,5 @@
+FROM python:3.3-alpine
+LABEL maintainer="Kilna kilna@kilna.com"
+RUN pip install python-lambda &&\
+    mkdir /lambda
+WORKDIR /lambda

Dockerfile-3.3

@@ -0,0 +1,5 @@
+FROM python:3.4-alpine
+LABEL maintainer="Kilna kilna@kilna.com"
+RUN pip install python-lambda &&\
+    mkdir /lambda
+WORKDIR /lambda

Dockerfile-3.4

@@ -0,0 +1,5 @@
+FROM python:3.5-alpine
+LABEL maintainer="Kilna kilna@kilna.com"
+RUN pip install python-lambda &&\
+    mkdir /lambda
+WORKDIR /lambda

Dockerfile-3.5

@@ -0,0 +1,5 @@
+FROM python:3.6-alpine
+LABEL maintainer="Kilna kilna@kilna.com"
+RUN pip install python-lambda &&\
+    mkdir /lambda
+WORKDIR /lambda

Dockerfile-3.6

@@ -4,9 +4,15 @@ Lightweight docker image for running and packaging python-based AWS lambda code.
 * [alpine-aws-python-lambda on docker hub](https://hub.docker.com/r/kilna/alpine-aws-python-lambda/)
 * [alpine-aws-python-lambda on github](https://github.com/kilna/alpine-aws-python-lambda)
 
+# Purpose
+
+I needed a Docker-based environment in which to host AWS python lambda functions for the purpose of testing and building them... python-lambda works well under virtualenv for development, but build and deployment automation require a clean and reproducible environment to operate in. Our CI system already supported Docker as a containerization sytem, so it was the obvious choice.
+
+In order to use this, you will have your project derive its own Dockerfile based on a base alpine-aws-python-lambda image corresponding to which version of Python you wish to run.
+
 # Usage
 
-An example of a usable project can be found in the [example/](./example/) directory.  This lambda function takes a JSON input file like the provided [event.json](./example/event.json) and returns an ASCII-art version of the text described in it.  The provided [Dockerfile](./example/Dockerfile) derives from this image and loads the current workspace into the image, then installs dependencies from the [requirements.txt](./example/requirements.txt) file.
+An example of a usable project can be found in the [example/](./example/) directory.  This lambda function takes a JSON input file like the provided [event.json](./example/event.json) and returns an ASCII-art version of the text described in it.  The provided [Dockerfile](./example/Dockerfile) derives from this image and loads the current workspace into the image, then installs dependencies from the [requirements.txt](./example/requirements.txt) file.  
 
 To build a docker image called _example-lambda-image_ with the example lambda function in it, run:
 
@@ -33,11 +39,39 @@ If you would like to see if your lambda function builds properly, run:
 $ docker run example-lambda-image lambda build
 ```
 
-If you would like to get a ZIP file of the lambda function suitable for uploading to Amazon, and the build log in one command:
+## Build and Test
+
+If you would like to build and test the lambda function and gather up the results, you can run:
 
 ```
-$ docker run example-lambda-image sh -c 'rm -rf build.log dist || true && lambda build &>build.log && tar -c build.log dist' | tar -x -v
+$ docker run example-lambda-image lambda_build_tar | tar -x -v
 build.log
+test.log
 dist/
 dist/2017-09-01-003647-example-lambda.zip
 ```
+
+Behind the scenes, what this script does is:
+
+* Removes any log and dist files from prior runs
+* Runs 'lambda build' and store the log in _/lambda/build.log_ in the container
+* If present and executable, run _/lambda/run_tests_ and store the log in /lambda/test.log in the container
+* Tars the log files, and the contents of the dist directory in /lambda on the container and pipes it to standard output
+* Untars the contents bundled up within the container, and extracts them into your current directory 
+
+## Python Version
+
+The example Dockerfile uses _:latest_ in the FROM line, which is currently the same as _:python-3.6_, but if you wish to use different python versions you can change this.
+
+For instance, if you want to use Python version 2.7 change the first line of your Dockerfile from:
+
+```
+FROM kilna/alpine-aws-python-lambda:latest
+```
+
+To:
+
+```
+FROM kilna/alpine-aws-python-lambda:python-2.7
+```
+

README.md

@@ -0,0 +1,14 @@
+#!/bin/sh
+
+# This file runs 'lambda build', saving the log to build.log, then tars both
+# the dist/ directory and the build.log file to STDOUT
+
+set -e
+cd /lambda
+rm -rf *.log dist &>/dev/null || true
+lambda build &>build.log
+if [ -x 'run_tests' ]; then
+  ./run_tests &>test.log
+fi
+tar -c *.log dist
+

bin/lambda_build_tar

@@ -1,3 +1,3 @@
-FROM kilna/alpine-aws-python-lambda
-COPY . /workspace
+FROM kilna/alpine-aws-python-lambda:latest
+COPY . /lambda
 RUN pip install -r requirements.txt

example/Dockerfile

@@ -0,0 +1,9 @@
+#!/bin/sh
+
+set -e
+set -o pipefail
+cd /lambda
+if [ `lambda invoke | md5sum | cut -d ' ' -f 1` != '5cd3139eadee0a85b2bb9f2164f3b6f6' ]; then
+  echo 'ERROR: md5sum of output returned by lambda invoke did not match expected results'
+fi
+