deploy to additional regions on release, resolves #83 and #86

developmentseed · Oct 16, 2020 · 9360696 · 9360696
1 parent 60f3406
commit 9360696
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.circleci/config.yml b/.circleci/config.yml
@@ -50,7 +50,7 @@ jobs:
             cd ..
             # deploy public Lambda layers
             pip install awscli
-            for region in us-east-1 us-west-2 eu-central-1
+            for region in us-east-1 us-west-2 eu-central-1 eu-west-2 eu-north-1
             do
               LVERSION="$(aws lambda publish-layer-version --region ${region} \
                 --layer-name geolambda --license-info 'MIT' \

diff --git a/README.md b/README.md
@@ -26,7 +26,7 @@ When using GeoLambda some environment variables need to be set. These are set in
 
 ### Lambda Layers
 
-If you just wish to use the publicly available Lambda layers you will need the ARN for the layer in the same region as your Lambda function. Currently, GeoLambda layers are available in `us-east-1`, `us-west-2`, and `eu-central-1`. If you want to use it in another region please file an issue or you can also create your own layer using this repository (see instructions below on 'Create a new version').
+If you just wish to use the publicly available Lambda layers you will need the ARN for the layer in the same region as your Lambda function. Currently, the latest GeoLambda layers are deployed in `us-east-1`, `us-west-2`, `eu-central-1`, `eu-west-2`, and `eu-north-1`. If you want to use it in another region please file an issue or you can also create your own layer using this repository (see instructions below on 'Create a new version').
 
 #### v2.0.0