Releases: NASA-IMPACT/veda-backend
v1.1.0-rc.16
v1.1.0-rc.16 (2023-11-27)
Fix
- fix(ci): upgrade github actions to resolve warnings (#254)
- Upgrade to github actions to resolve outdated node version warnings
- Add cdk deploy output to file to resolve set-output warning
- Conventional PR linter if not not updated: we may need to remove or
replace if this upgrade
PR
is not accepted. For now, there is a warning in the pr action about
forcing linter to run on an upgraded node version.
Parent issue NASA-IMPACT/veda-architecture#345 (7e348cf
)
v1.1.0-rc.15
v1.1.0-rc.14
v1.1.0-rc.13
v2.0.1
v2.0.1 (2023-11-16)
Fix
- fix(raster): pin rio-tiler 6.2.3.post1 (#250)
What
Pin a post rio-tiler release that supports zonal statistics upgrades
while a map zooming issue is investigated
Why
v1.1.0-rc.12
v1.1.0-rc.11
v2.0.0
v2.0.0 (2023-11-13)
Breaking
- feat!: titiler upgrade, optional custom base path for apis, optional cloudfront (#244)
What
- adds optional configuration to deploy all endpoints with a custom root
path (i.e./api/stac
and/api/raster
) #229, #241 - adds support for using a cloudfront as a reverse proxy #229, #241,
#245 - titiler-pgstac upgraded from 0.2.3 to 0.8.0 #239
- titiler upgrade for custom colormap configuration #243
How tested
A temporary test stack was deployed to confirm that raster-api works as
expected and that the two-subdomain staging-stac and staging-raster
pattern is still supported. The pre-deploy diff action for this
pr
confirms that the raster API lambda will be upgraded and no domain name
changes will be caused. (b5e2701
)
v1.1.0-rc.10
v1.1.0-rc.10 (2023-11-10)
v1.1.0-rc.9
v1.1.0-rc.9 (2023-11-09)
Breaking
- fix(apis)!: overwrite api host when provided in config (#245)
What
- When a custom host is configured, overwrite the host in the api
integration (bring back the parameter mapping method introduced in #229) - Include origin_path in cloudfront ingest api behavior. Note: this path
will not work until the root_path is changed toapi/ingest
in the
ingest api - Domain construct now only generates custom subdomains for endpoints
when configured (existing stacks must provide new configuration
variable). Note: indentation changes that wrap all subdomain constructs
make the change appear larger than they really are. The change removes
an unused shared subdomain construct and only generates api-specific
subdomains when create subdomains configuration is true.
Environment variable changes
New
VEDA_CUSTOM_DOMAIN
optional configuration to provide a complete url
for host overrides in lambda APIs (i.e. dev.somedomain.com
)
Removed
VEDA_DOMAIN_SHARED_SUBDOMAIN
is no longer used (logic is managed with
custom subdomains config below)
New+Breaking
VEDA_DOMAIN_CREATE_CUSTOM_SUBDOMAINS
boolean defaults false. Existing
deployments with custom subdomains for each raster and stac api
endpoints need to set this variable to TRUE. (7072ca2
)
-
fix(routes)!: ingest api root path is /api/publish (
ab10741
) -
fix(apis)!: overwrite host in api integration if custom host provided (p2) (
6c66f06
) -
fix(apis)!: overwrite host in api integration if custom host provided (
9edc296
)
Unknown
- fix(domain)! only create custom api subdomains when configured (
c6bc465
)