You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 21, 2019. It is now read-only.
With #24 and #21 I think it's clear that we should have a way to create/update the docker image and also to have the lambda layer deploy
As mentioned in #26 we should only focus on the latest GDAL version (3.0.1, 2.4.2 and master). For Python version it's a little bit difficult but I think supporting 3.6 and 3.7 should be enought ?
so at the end the process should create
gdal2.4.2-py3.7 (layer + docker image)
gdal2.4.2-py3.6 (layer + docker image)
gdal3.0.1-py3.7 (layer + docker image)
gdal3.0.1-py3.6 (layer + docker image)
gdalmaster-py3.7 (layer + docker image)
gdalmaster-py3.6 (layer + docker image)
To achieve this I think we should also refator the whole repo architecture
With #24 and #21 I think it's clear that we should have a way to create/update the docker image and also to have the lambda layer deploy
As mentioned in #26 we should only focus on the latest GDAL version (3.0.1, 2.4.2 and master). For Python version it's a little bit difficult but I think supporting 3.6 and 3.7 should be enought ?
so at the end the process should create
To achieve this I think we should also refator the whole repo architecture
every commit to master should trigger build/deploy
The text was updated successfully, but these errors were encountered: