s3-resource-simple/script/run

#!/bin/sh

set -e

source=$1

if [ -z "$source" ]; then
  echo "usage: $0 </full/path/to/dir/or/file>"
  exit 1
fi

json=$(cat .env.json)

docker build -t 18fgsa/s3-resource-simple .

echo $json | docker run \
  -i \
  --rm \
  -v $source:/tmp/input \
  18fgsa/s3-resource-simple \
  /opt/resource/out /tmp/input
finish up the `out` script also add a `run` script for testing purposes 2016-03-10 09:01:02 +01:00			`#!/bin/sh`

			`set -e`

			`source=$1`

pass the AWS credentials through the Concourse source data Concourse pipelines dont have a way of setting environment variables, and this is consistent with how https://github.com/concourse/s3-resource works. 2016-03-10 16:57:12 +01:00			`if [ -z "$source" ]; then`
			`echo "usage: $0 </full/path/to/dir/or/file>"`
finish up the `out` script also add a `run` script for testing purposes 2016-03-10 09:01:02 +01:00			`exit 1`
			`fi`

pass the AWS credentials through the Concourse source data Concourse pipelines dont have a way of setting environment variables, and this is consistent with how https://github.com/concourse/s3-resource works. 2016-03-10 16:57:12 +01:00			`json=$(cat .env.json)`
finish up the `out` script also add a `run` script for testing purposes 2016-03-10 09:01:02 +01:00
pass the AWS credentials through the Concourse source data Concourse pipelines dont have a way of setting environment variables, and this is consistent with how https://github.com/concourse/s3-resource works. 2016-03-10 16:57:12 +01:00			`docker build -t 18fgsa/s3-resource-simple .`
accept the incoming JSON config data 2016-03-10 09:57:41 +01:00
			`echo $json \| docker run \`
			`-i \`
finish up the `out` script also add a `run` script for testing purposes 2016-03-10 09:01:02 +01:00			`--rm \`
			`-v $source:/tmp/input \`
put the docker image under the 18F namespace 2016-03-10 09:20:05 +01:00			`18fgsa/s3-resource-simple \`
finish up the `out` script also add a `run` script for testing purposes 2016-03-10 09:01:02 +01:00			`/opt/resource/out /tmp/input`