v5.0.1

v5.0.1 (2024-05-07)

Fix

• fix(release): make ingest api root path optional (#370)

Changed

• fix(ingest): default empty string for root path in ingest api
  construct (7f58da4)

v5.0.0

v5.0.0 (2024-05-06)

Breaking

• feat(release)!: release db, stac and ingest api, add otel (#368)

Breaking

• feat(api)!: ingest-api/docs auth flow

Notes

Breaking: VEDA_COGNITO_DOMAIN configuration now required along with
one time administrator step to update existing user pool client allowed
callback urls with the ingest-api's URL

Added

• feat(otel): add otel to ingest API
• feat: database subnet configuration and externally triggered ci action improvements
• feat: configurable subnet ids

Changed/Updated

• chore: run ingest tests with coverage in local test script
• ci: update predeploy actions

Fixed

• fix: cast sub as str
• fix: update get_username function
• fix: change get username function
• fix: cognito domain env var
• fix(stac-api): next link and trailing slash bug in stac api url
• fix: merge upstream dependency fixes
• fix(db)!: update collection summaries on load items
• fix: resolve dependency and node warnings and fix stac browser deployments with cloudfront
• fix: stac browser catalog url with cloudfront
• ci: fix vcs release in deploy and upgrade action versions
• fix: api dependencies upgrade
• fix(ci): remove new openapi test to unblock release
• fix: revert openapi spec addition changes
• fix(api): do not override ingest api subnet config
• chore: test api responses against openapi spec
• fix: update condition for setting storage_encrypted
• chore: merge subnets changes into ci branch
• fix(ci): updates for veda deploy(6fc9ded)

v1.1.0-rc.58

v1.1.0-rc.58 (2024-05-06)

Fix

• fix(ingest): default empty string for root path in ingest api construct (#369)

What?

• Allow ingest-api to be deployed without a custom root path by setting
  the default config for fastapi root path parameter to None.

Why?

• When the ingest API is deployed to a stack without a cloud front and
  custom host it should not apply an additional root path.

How tested

Deployed to a test branch using a custom subdomain instead of a
cloudfront with custom root path. (c23dd1e)

• fix(ingest): default empty string for root path in ingest api construct (13de8de)

• fix(ingest): default empty string for root path in ingest api construct (77996a7)

v1.1.0-rc.57

v1.1.0-rc.57 (2024-05-06)

Fix

• fix: cast sub as str (#367)

Issue

Link to relevant GitHub issue

What?

• Cast sub as str and remove default None since that will be cast
  as str which we want to avoid

>>> token = { }
>>> x = token.get("sub", None)
>>> str(x)
'None'
>>> exit()

Why?

• We were receiving this error when trying to kick off a
  /dataset/publish/ workflow
  1 validation error for Ingestion\ncreated_by\n str type expected (type=type_error.str) and, to be safe, we are casting sub as str

Testing?

• Locally deployed on dev and ran /dataset/publish/ successfully
  https://4e76fa52-1de6-41a5-b364-691fb1cc69f4.c18.us-west-2.airflow.amazonaws.com/dags/veda_ingest_raster/graph?run_id=0767fd24-461d-481f-85eb-2ebb4662d144_617296f2-18e1-4711-9961-8a542bb8958b_0&execution_date=2024-05-02+19%3A54%3A13.422305%2B00%3A00 (04b0b64)

• fix: remove None default (57daf56)

• fix: cast sub as str (f6270b2)

v1.1.0-rc.56

v1.1.0-rc.56 (2024-04-29)

Fix

• fix: update get_username function (#365)

Issue

NASA-IMPACT/veda-data-airflow#134
#347

What?

• Update get_username to fall back on sub if username doesn't exist
  in token
• Added some more logging statements to make debugging easier in the
  future

Why?

• This fix is to enable a successful workflows API run since the
  workflow API passes a token to backend API and it's currently erroring
• Also, sub is a more definitive identifier because it represents a
  unique identifier compared to username

Testing?

• Relevant testing details (28afca4)

• fix: revert to use default value in get_username (f640fdf)

• fix: update to throw is username or sub are not found in token (dbb62fb)

• fix: add correct escape sequence to logging (5466404)

• fix: update get_username and add logging (4e38e89)

v1.1.0-rc.55

v1.1.0-rc.55 (2024-04-26)

Fix

• fix: change get username function (#361)

Change Ingestion created_by param to use get_username auth function (eb6a922)

v1.1.0-rc.54

v1.1.0-rc.54 (2024-04-26)

Fix

• fix: cognito domain env var (#360)

what

this pr updates the env variable name used for cognito domain (now
matches workflows variable name) (769c647)

• fix: use standard env name for cognito domain (e021ec2)

v1.1.0-rc.53

v1.1.0-rc.53 (2024-04-26)

Fix

• fix(stac-api): next link and trailing slash bug in stac api url (#358)

What

Fix problem in which a stac-fastapi deployed behind a proxy (i.e.
customdomain.com) with a custom root path (i.e. /api/stac)

• Fixed: API does not properly resolve customdomain.com/api/stac ->
  customdomain.com/api/stac/
• Fixed: API does not properly use custom root path in next links of
  paginated responses customdomain.com/api/stac/... links are returned
  as customdomain.com/... without the custom root path.

The correction is to remove the gateway configuration from the Mangum
ASGI handler for the stac-api handler.

Refs

• Fastapi behind a
  proxy
• Mangum configuring an adaptar instance with
  api_gateway_base_path
  pattern that we use and need for titiler/raster-api and ingest-api

Issue

#343

Testing?

• I deployed this change manually to the dev veda-backend stack and
  confirmed that the stac-api url is properly resolved and that the next
  links now properly include the root path. (2424fe5)

• fix(stac-api): do not overwrite api_gateway_base_path in stac-api handler (09717aa)

v1.1.0-rc.52

v1.1.0-rc.52 (2024-04-24)

Breaking

• feat(api)!: ingest-api/docs auth flow (#356)

What?

• Breaking: VEDA_USERPOOL_DOMAIN_BASE_URL configuration now required
  along with one time administrator step to update existing user pool
  client allowed callback urls with the ingest-api's URL
• Updates ingest-api auth flow: use redirect to cognito UI for secure
  user password entry via Authorize button in swagger docs
• Removes outdated whoami auth response model
• Upgrades ingest-api fastapi to patched version 0.9.1
• Improves ingest-api configuration and deployment documentation

Why?

• Token/ endpoint behavior sluggish via. swagger docs and it is not
  desirable to enter secrets in a string input form (the token/ endpoint
  is still supported for programmatic access)

Testing?

• Deployed manually to dev stack and updated allowed callbacks of dev
  cognito user pool client
• Obtained tokens via Authorize button and /token endpoints
• Created, then deleted one collection (5c3cea4)

v1.1.0-rc.51

v1.1.0-rc.51 (2024-04-23)

Feature

• feat(otel): add otel to ingest API (#342)

Co-authored-by: smohiudd <[email protected]> (9f0289b)