NASA-IMPACT / NASA-IMPACT/veda-deploy
Investigate adding staging as an environment
Open
@anayeaye is already working on this.
Since Oct 7, 2024.
- Dominant language
- Python
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Our staging stack is in the UAH AWS account which, historically, we didn't have the correct role that allowed us to set up an environment to use veda-deploy. We should have a role that allows us to deploy staging using the veda-deploy pipeline now.
Acceptance Criteria
- staging environment is set up
- staging can be deployed using veda-deploy
- automated deployment to staging on merge into main removed from veda-backend
Too soon while managing the legacy deployments of these:
- automated deployment to staging on merge into main removed from veda-auth (will be replaced by auth-central)
- automated deployment to staging on merge into main removed from veda-data-airflow (still needs stand alone deployment to staging while supporting two different vpcs)
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.
Assessment
This issue has not been assessed yet.