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)

v1.1.0-rc.33

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

Feature

• feat: local integration tests (#286)

This PR makes it as simple as possible to run CI checks (linting and
testing). It also includes conditional logging when those tests fail.

It also fixes the local ingestor container's build, which was
overwriting the directory into which requirements were being installed

Closes #285 (3e41a4f)

v1.1.0-rc.32

v1.1.0-rc.32 (2024-02-20)

Feature

• feat: expose rds proxy to be used for veda endpoints (stac/raster) (#299)

In this pull request, if a user decides to use RDS Proxy (by defining
the environment variable VEDA_DB_USE_RDS_PROXY=true), an RDS proxy will
be provisioned with all its necessary security groups. Additionally, AWS
Secret Manager secrets for the proxy will be provisioned and returned to
be used for VEDA endpoints.

Other improvements include:

• Changed the subnet type from PRIVATE_ISOLATED to PRIVATE_WITH_EGRESS,
  aligning with our documentation that specifies the creation of a
  'private' subnet.
• In this
  line,
  the environment variable is now converted to uppercase to eliminate
  errors in case the user enters a lowercase RDS type or size. Despite the
  type being uppercase, the stack might throw an error if not explicitly
  converted to upper.
• In this
  line,
  the platform is explicitly added in the Docker file to prevent random
  errors that may occur if the image was built with a different
  architecture.

Here,
a cache has been added for requesting the secret manager, enhancing
performance.

We created a stress test scenario with and without RDS proxy and the
results were as
follow (3484ab2)

v1.1.0-rc.31

v1.1.0-rc.31 (2024-02-16)

Chore

• chore: hotfix from main change search base condition (#307)

What

Pull hotfix from main in #303 (b5d5e3b)

Fix

• fix: update iam role name for stac ingestor to be unique across stages (#309)

Issue

• #308

Changes Made

• updated the role name to use stack_name since the original stage
  variable would default to runner across different stages causing
  deployments to dev to fail

Testing Done

• Locally deployed to dev successfully and confirmed that the previous
  resource delta-backend-staging-stac-ingestion-api-runner still exists
  and that stac-ingestion-api-veda-backend-uah-dev-role was created and
  the dev deployment succeeded (59cd963)

• fix: update iam role name for stac ingestor to be unique across stages (832e348)

• fix: migrate stamen map references to stadia maps (#301)

Description

• This PR migrates Stamen Map references to use Stadia Maps (full
  migration notes
  here)
• The migration is setup with my DevSeed email and to work with
  *.delta-backend.com domain

Related Issues

#291

Changes Made

• updates stac-viewer.html references from stamen maps to stadia maps

Testing Done

- Page now shows
map (385e611)

• fix: migrate stamen map references to stadia maps (aa2f603)

v3.0.1

v3.0.1 (2024-02-15)

Fix

• fix: change search base condition causing key error (#303) (d7a0a51)

v3.0.0

v3.0.0 (2024-02-14)

Breaking

• feat!: titiler upgrades, add render to stac, add preliminary ingest system (#292)

What

• stac-api dynamically adds render properties for collections configured
  with information about how assets should be rendered on a map
• titiler and dependencies upgrade
• base ingest system now rolled into veda-backend deployments (api,
  dynamodb, bulk loading lambda)
  • includes new tests in ingest_api
  • introduces new components in docker-compose
• introduces new auth user pool and client requirement and required
  environment variables (breaking)
• introduces new required env variables in externally triggered github
  cdk-deploy/action.yml
• preliminary in raster-api work to handle alternate asset references
  (longer term fix may be upstream)
• linting package upgrade

Breaking

The integrated ingest system requires new configuration variables and
depends on a cognito user pool and client. This configuration will
likely be optional in future releases.

New required environment variables

VEDA_USERPOOL_ID=us-west-X_XXX
VEDA_CLIENT_ID=XXX
VEDA_INGEST_ROOT_PATH=/api/ingest
``` ([`2734b49`](https://github.com/NASA-IMPACT/veda-backend/commit/2734b49abceb190c5b3e63b4113bd620c2cc0f65))