j40-cejst-2/infrastructure/README.md

# Current steps for local & stg:

## Assumptions

Make sure you have previously run

`npm install`

and this assumes you have set up an AWS account and have your CLI programmatic access stored in:

OSX:
`~/.aws/credentials`

Windows:
`C:\Users\USERNAME\.aws\credentials`

## Create ACM Certificate

This only needs to be run once for the `stg` environment.  Prd (not yet created: tbd) will be assuming some other certificate arn will be used.

    `npx serverless create-cert`

You'll have to grab the arn of the certificate from the log output or go into the console to get it, looks like the plugin doesn't work any more.  Set CLOUDFRONT_CERTIFICATE_ARN in sit to that value.

## How To Deploy

    `sls deploy --aws-profile <<your profile name from ~/.aws/credentials>> --stage stg --verbose`

* Note: if sls doesn't work for you, try running this command inside /infrastructure: 

    `./node_modules/.bin/serverless deploy --aws-profile <<your profile name from ~/.aws/credentials>> --stage stg --verbose`

# Warning! This section on is currently unimplemented, partially incorrect, and untested.

## Testing

The examples can be run several different ways

### Local

The `package.json` file incluses several examples to run against the local source code.  The actual 
tasks will execute within AWS, so an `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` must be set in
the `test.env` file.

```bash
$ cd ./functions/detect-changes-for-worker
$ npm run test:gdal
```

### Lambda invoke

The deployed lambda functions can be directly invoked with the `serverless invoke` function.

```bash
$ cat ./functions/detect-changes-for-worker/events/gdal.json | sls invoke -s sit -f DetectChangesForWorker
```

New event files can be created to perform one-off data processes.