v1.1.0-rc.42

v1.1.0-rc.42 (2024-03-11)

Fix

• fix(api): do not override ingest api subnet config (#329)

Fixed

• Resolves a recently introduced bug that moved the ingest api lambda to public subnets when the database was configured as public. Now the ingest-api lambda is correctly always deployed to private subnets. (09e74ec)

v1.1.0-rc.41

v1.1.0-rc.41 (2024-03-09)

Chore

• chore: test api responses against openapi spec (#327)

Co-authored-by: Stephen Kilbourn <[email protected]> (905d4c0)

v1.1.0-rc.40

v1.1.0-rc.40 (2024-03-05)

Chore

• chore: merge subnets changes into ci branch (#325) (5400ccf)

Fix

• fix(ci): updates for veda deploy (#324)

Issue

NASA-IMPACT/veda-deploy#25

What?

• Updates needed to deploy using veda-deploy
• Update version of GitHub actions

Why?

• for veda-deploy to be able to pass env vars from one stack to
  another

Testing?

• Ran deployment using veda-deploy until successful (3a83513)

v1.1.0-rc.39

v1.1.0-rc.39 (2024-03-05)

Feature

• feat: configurable subnet ids (#323)

What?

• Allows users to specify the subnet IDs to be used for the database

Why?

• Since we don't always get to create our own VPC, the subnets
  associated with it are not always one or the other type. We've had
  issues in the past with the private subnet type not being available in
  the VPC (PRIVATE_ISOLATED, PRIVATE_EGRESS, etc. This allows users to
  specify the subnet ids so we don't rely on a specific type.

Testing?

• Deployed and manually checked that the database and the ingest lambdas
  were associated to the subnets provided (6d51efc)

v4.0.0

v4.0.0 (2024-02-26)

Breaking

• feat!: rds proxy, stac api fixes, ingest api improvements, new local testing docs (#322)

What?

• RDS Proxy can be enabled in configuration
• VPC subnet selection change from PRIVATE_ISOLATED to
  PRIVATE_WITH_EGRESS (breaking for VPCs with ISOLATED subnets)
• Local testing updates
• Bugfixes in render extension of raster-api for collections with no
  items (i.e. linking external data sources) and for item search results
  with collection property excluded
• Stac-api viewer base map fixed
• Stac ingestor iam role name updated to be unique across stages
• PR template added
• Extraneous format conversions for DDB stac data queue removed
• Cloudfront additional behavior mapping now added after the
  distribution is created (4eae503)

v1.1.0-rc.38

v1.1.0-rc.38 (2024-02-26)

Fix

• fix(ingest): float proj issue (#316)

What

Fixes the float epsg code issue caused by dynamodb serialization

Picked up the fix from
developmentseed/eoapi-cdk#26

How test

Tested by running ingest from here:
https://mv5tl66nca.execute-api.us-west-2.amazonaws.com/
Test item:
https://vr3ofct5u8.execute-api.us-west-2.amazonaws.com/api/stac/collections/geoglam/items/CropMonitor_202205_test_2

import pystac

item = pystac.Item.from_file("https://vr3ofct5u8.execute-api.us-west-2.amazonaws.com/api/stac/collections/geoglam/items/CropMonitor_202205_test_2")
print(item.properties["proj:epsg"]) # should give 4326 instead of 4326.0

4326
``` ([`0e2bc31`](https://github.com/NASA-IMPACT/veda-backend/commit/0e2bc3105ba188bf89d5ef274b89dc44b1a20612))

v1.1.0-rc.37

v1.1.0-rc.37 (2024-02-26)

Fix

• fix: remove nested if (59fcef2)

• fix(routes): make behaviors additive, do not replace (3587f12)

v1.1.0-rc.36

v1.1.0-rc.36 (2024-02-26)

Fix

• fix: migrate stamen map references to stadia maps raster api (#321)

Issue

#291

What?

• Update Stamen Maps to Stadia Maps

Why?

• Addressed this changed in a previous
  PR but didn't
  realize that I needed to update the raster api as well

Testing?

• Local testing on vscode without deploying to dev (3cc699a)

Unknown

• fix:Migrate from Stamen to Stadia Maps for Raster API (5c4b9df)

v1.1.0-rc.35

v1.1.0-rc.35 (2024-02-23)

Fix

• fix: update stac viewer endpoint value (#311)

Issue

#291

What?

• Updated the endpoint value for the STAC viewer in order to properly
  render the collections on the webpage.
• Added a PR template so that all new PRs will have a template for
  reference

Why?

• The endpoint is https://dev.openveda.cloud/collections which is
  incorrect which causes the collections filter to fail in the STAC
  viewer.

Screen.Recording.2024-02-16.at.4.26.57.PM.mov

Testing?

• I didn't locally deploy or anything but here is the working
  collections link

Notes

• I think we could technically also update
  https://github.com/NASA-IMPACT/veda-backend/blob/develop/stac_api/runtime/src/app.py#L79
  to be:
  {"request": request, "endpoint": str(request.url).replace("/index.html", "/api/stac")}, if that's preferred (c672098)

v1.1.0-rc.34

v1.1.0-rc.34 (2024-02-22)

Fix

• fix: upgrade titiler.pgstac to 0.8.3 (#318) (252253f)