NASA-IMPACT / NASA-IMPACT/veda-deploy
Pass `VECTOR_VPC` and `VECTOR_SECRET_NAME` from `veda-features-api` to `veda-data-airflow`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Description
veda-data-airflow consists of dags for vector ingests that take in VECTOR_VPC and VECTOR_SECRET_NAME env vars. As part of the veda-deploy workflow, these env vars should be passed from the veda-features-api-cdk deployment for veda-data-airflow to use.
Something to consider
veda-features-api-cdk is an optional service that can be omitted. But its omittance shouldn't stop veda-data-airflow from deploying. So, adding veda-features-api-cdk in the needs of veda-data-airflow directly will not work - we'll need a workaround.
AC
-
veda-data-airflowreceives the two env vars fromveda-features-api-cdkdeployment
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/cicd.yml around line 163 and trace how veda-features-api-cdk and veda-data-airflow deployments expose and consume environment variables. Verify the workflow behavior when the optional veda-features-api-cdk service is omitted. Done means veda-data-airflow receives VECTOR_VPC and VECTOR_SECRET_NAME when available and still deploys without that service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100