All IAC changes are configurable and current GHGC deployments should be maintained unchanged with updates to the configuration provided.
Raster API has an upgraded pgstac-titiler and titiler version upgrade that cause breaking endpoint changes as well as a new non-breaking addition of a custom colormap.
This brings over a year's worth of upstream commits but a lot of the changes were added here and upstream so the change set isn't too terrible.
Env variables
Changed
VEDA_(STAC|RASTER)_PATH_PREFIX -> VEDA_(STAC|RASTER)_ROOT_PATH (same value new property name for stac fast api root path override instead of updating all routes individually with a path prefix)
VEDA_HOST - > VEDA_CUSTOM_HOST (when provided, complete host url will be used in lambda parameter mapping to overwite host header)
VEDA_DB_RDS_TYPE - > VEDA_DB_RDS_INSTANCE_SIZE and VEDA_DB_RDS_INSTANCE_CLASS
Now we only generate custom subdomains when enabled in configuration (no change for GHGC instances)
Routes
The project can now generate a cloudfront distribution when configured
stac-api, raster-api, and ingest-api behaviors are currently hard coded with root paths /api/stac, /api/raster, and /api/ingest. We will make this configurable in the future
Current support requires an existing s3 static website (browser) and route 53 zone id and name
Database Dockerfile
VEDA just uses FROM public.ecr.aws/sam/build-python3.9:latest but I left FROM --platform=linux/amd64 ... as is in GHGs Dockerfile (but I did keep the rest of the upstream diff)
What is changed
Env variables
Changed
VEDA_(STAC|RASTER)_PATH_PREFIX->VEDA_(STAC|RASTER)_ROOT_PATH(same value new property name for stac fast api root path override instead of updating all routes individually with a path prefix)VEDA_HOST- >VEDA_CUSTOM_HOST(when provided, complete host url will be used in lambda parameter mapping to overwite host header)VEDA_DB_RDS_TYPE- >VEDA_DB_RDS_INSTANCE_SIZEandVEDA_DB_RDS_INSTANCE_CLASSVEDA_DB_RDS_STORAGE_ENCRYPTED- >VEDA_DB_RDS_ENCRYPTIONAdded optional configuration
VEDA_DB_RDS_INSTANCE_CLASSVEDA_DB_RDS_ENGINE_FULL_VERSIONVEDA_DB_RDS_ENGIN_MAJOR_VERSIONVEDA_DOMAIN_CREATE_CUSTOM_SUBDOMAINSConstruct Changes
Domain
Now we only generate custom subdomains when enabled in configuration (no change for GHGC instances)
Routes
/api/stac,/api/raster, and/api/ingest. We will make this configurable in the futureDatabase Dockerfile
VEDA just uses
FROM public.ecr.aws/sam/build-python3.9:latestbut I leftFROM --platform=linux/amd64 ...as is in GHGs Dockerfile (but I did keep the rest of the upstream diff)