NASA-IMPACT / NASA-IMPACT/veda-deploy

Deploy Features API to Production

Open
#57 5 comments 0 reactions 1 assignee View on GitHub

@botanical is already working on this.

Since Dec 11, 2024.

Dominant language
Python
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Description

VEDA Features API has been refactored to use cdk instead of terraform and is included in this repo: https://github.com/NASA-IMPACT/veda-features-api-cdk. Features API is currently deployed in the UAH account as a staging environment. The main stakeholder/user of this service is the EIS Fire team who ingest daily data to the database. To support more stables services and include the deployment in veda-deploy, Features API must be deployed to MCP.

  • deploy Features API to MCP production environment. There is currently a switch in veda deploy for Features API which is set to false.
  • Create db with snapshot of veda-wfs3-west2-staging rds and use it to create the production features api
  • Cutover VEDA dashboard to production features API and update external reference in production catalog for eis_fire_perimter dataset https://openveda.cloud/api/stac/collections/eis_fire_perimeter

Acceptance Criteria

  • Features API is deployed to MCP using veda-deploy and is hosting EIS Fire data
  • Production Features API is used in VEDA dashboard for eis_fire_perimeter dataset

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.