Releases: NASA-IMPACT/veda-backend
v1.1.0-rc.25
v1.1.0-rc.25 (2024-01-23)
Fix
- fix: update ingest api subnet types and log format and update pre-commit config (#281)
Description
- This PR updates the subnet type for the ingest api handler to use
private subnets. - This PR also updates the pre-commit yaml file
Related Issues
Changes Made
- Update ingest api to use private subnets
- Update
pre-commit-config.yaml
to updatemypy
rev and add
additional_dependencies
Testing Done
I manually update the dev ingest api lambda to have private subnets
(previously, they were configured with public subnets) and tested the
dev delta /token
endpoint and the lambda endpoint itself. (be30a80
)
-
fix: update ingest api subnet types and log format and update pre-commit config (
56babaa
) -
fix(ingest): try #2 to return failed login exception for debugging (#274)
Another attempt to expose the cause of the token endpoint timeout (8e765e4
)
- fix(ingest): return failed login exception for debugging (
4f28e09
)
v1.1.0-rc.24
v1.1.0-rc.23
v1.1.0-rc.22
v1.1.0-rc.21
v1.1.0-rc.21 (2024-01-08)
Fix
What
- Add updates from PR #246 and unpin rio-tiler temporary post release
version - Pin starlette from PR #268
- Unpin post release rio-tiler version #259 (
7a29883
)
-
fix(raster): incorporate updates from #246 and unpin rio-tiler version (
efe8bb0
) -
fix(ingest): fix MCP 500 errors
- remove secret hash as required
- remove cog_default validator (
23dca01
)
v1.1.0-rc.20
v1.1.0-rc.19
v1.1.0-rc.19 (2023-12-19)
Feature
-
feat(ingest): CDK + docker changes to support ingest_api (
1d758cd
) -
feat(ingest_api): Copy ingest runtime code from veda-stac-ingestor (
8f3575e
)
Fix
- fix(ingest): try to fix dev actions (#261)
Fixes failing dev test actions (956330e
)
-
fix(tests): try another test fix (
84288ae
) -
fix(tests): add aws region (
8069bce
) -
fix(tests): add missing config to ingest tests (
59732b6
) -
fix(tests): add tests to pr action (
b8380e6
) -
fix(ingest): test dependency fix (
6c3119a
) -
fix(actions): adjust deploy -> deploy-dev (
58c9ec3
) -
fix(actions): adjust deploy -> deploy-dev (
f07171b
) -
fix(ingest): rename data access role env var (
e97fce7
) -
fix(ingest): remove env secret management (
50d6251
) -
fix(ingest): remove unused ssm function (
a0377e3
) -
fix(docker): port mismatch specific to GH actions (
e634dd1
) -
fix(lint/ingest): minor bugfixes and lint fixes (
3dd40c7
) -
fix(ingest): route changes to support ingest via CF, env var changes (
81eb0ea
)
Unknown
v1.1.0-rc.18
v2.1.0
v2.1.0 (2023-12-11)
Feature
- feat: release stac-browser and fixes (#256)
What
- New eoapi-cdk construct
for deploying
a radiant earth
stac-browser - Updates to github actions versions to resolve node version warnings
- Adds support for externally triggered deployment actions
- Adds bootstrap-qualifier support for deploying to an aws account with
a non-standard cdk toolkit - Fixes permissions boundary construct
- Deployment requires an updated aws-cdk version (
0ce5c2e
)
v1.1.0-rc.17
v1.1.0-rc.17 (2023-12-04)
Documentation
Feature
- feat(browser): use eoapi-cdk to build a radiant earth stac browser (#257)
What
Added
- Add eoapi-cdk construct
for deploying a
radiant earth
stac-browser - Supports stacks that are deployed with either a custom subdomain (i.e.
<stage>-stac.delta-backend.com
) or cloudfront with custom routes (i.e.
<cfdomain>.com/api/stac
). - Add a construct to provision a new s3 website if an existing bucket is
not provided in configuration
Changed
- aws-cdk-lib(s) version update
- routes construct updated to use the bucket from the new s3 website
construct as origin (instead of just an existing bucket). - Docs updated
> Note 1.
There is a hack in the PR to work around a sequencing issue: neither the
https app id nor the stac api construct url are available at the time
that the eoapi-construct builds the stac-browser (i.e. this is not a
valid url string for the stac catalog:
https://${Token[TOKEN.189]}.execute-api.uswest-2.amazonaws.com
). To
work around this we are able to infer what the STAC catalog url will be
based on configuration for the cloudfront or subdomain.
> Note 2.
based on work introduced in pr #222 (with updates for current
veda-backend)
Source issue
NASA-IMPACT/veda-architecture#305
How tested
- deployed a test stack with cloudfront & browser
- pre-deploy cdk diff looks good (runner builds stac-browser)
- tested custom domain case (i.e.
<stage>-stac.delta-backend.com
) (730b05b
)
-
feat(browser): create s3 static website as a separate construct and enable deploying a stac browser for a stac-api with a custom subdomain (
75488e8
) -
feat(browser): use eoapi-cdk to build a radiant earth stac browser for instances with a cloudfront (
184382c
)
Unknown
- fix infer catalog url for app with service specific subdomains (
881d3e9
)