Releases: NASA-IMPACT/veda-backend
Releases · NASA-IMPACT/veda-backend
v1.1.0-rc.61
v1.1.0-rc.60
v1.1.0-rc.60 (2024-05-15)
Feature
- feat: enable cloudfront logging (#375)
Issue
What?
- Enable logging on the cloudfront distribution. Setting
enable_logging
to true will create an S3 bucket to write logs to with
the necessary permissions for cloudfront to successfully send logs.
Why?
- Best practices
Testing?
- Deployed to UAH dev and MCP test (
3311b28
)
v1.1.0-rc.59
v1.1.0-rc.59 (2024-05-13)
Fix
- fix: backend monitoring changes (#371)
Changes to observability in backend APIs:
- Include monitoring for STAC API endpoints
- service dimension change for ingest api (incorrectly had
"raster-api"), add monitoring to ingest handler - include path params and post body in logs
- include stage dimension in metrics to distinguish between instances
(i.e. dev, staging, etc.) - include metrics for each api path (i.e. collections/,
collections/{collection_id}, mosaic/register, etc.
Testing
v5.0.1
v5.0.0
v5.0.0 (2024-05-06)
Breaking
- feat(release)!: release db, stac and ingest api, add otel (#368)
Breaking
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
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
)
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
asstr
and remove defaultNone
since that will be cast
asstr
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 castingsub
asstr
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
)
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
ifusername
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 tousername
Testing?
- Relevant testing details (
28afca4
)