Jason Maurer

Hey guys, thanks for filing the issue and the PR. I'm not sure what the purpose of adding these coordinates would be. I'm assuming they are not the exact coordinates...

Yeah, I think latency calculations are much more complicated than simply finding the nearest data center. Might be useful to add in the future. I do see @AbhaysinghBhosale's point in...

Can you update the data structure to be more clear on what the coordinates are for? Instead of: ``` latitude: ... longitude: ... ``` I'm thinking something like this would...

In fact, it would be better if you could get the actual data center locations (or as close as possible) as outlined [here](https://www.turnkeylinux.org/blog/geoip-amazon-regions) and make the structure: ``` location: {...

Hi, you are not missing anything. A custom dictionary isn't currently supported. But I'd be open to a PR for it :)

Have the same issue. Here is the workaround I've been using with JQ (a command line JSON parser) and query data for the external Terraform provider: ```hcl data "external" "main"...

See commit in my fork with how I got around it. Not ideal... but it fixes it for the time being. https://github.com/jsonmaur/lambda-audio/commit/1117e428241579d343ce2f3cccf37d0e3e52ad86

Mine still seems to be running fine on Node 10.x. I have the libgomp.so.1 deployed under the `lib64` folder, then set this environment variable: ``` LD_LIBRARY_PATH=node_modules/lambda-audio/lib64:$LD_LIBRARY_PATH ``` This is assuming...

Same issue here. `sam package`/`sam deploy` should accept the `--env-vars` flag. My current workaround is to use CF parameters, since `sam package`/`sam deploy` are aliases for `cloudformation package`/`cloudformation deploy`. ######...

Works fine for me when I run `sam local invoke --env-vars env.json`. `--env-vars` seems to override the parameters.