NASA-AMMOS / NASA-AMMOS/plandev
Aerie Dev Deployment Improvements
Open
@skovati is already working on this.
Since Jun 22, 2023.
deployment
next
- Dominant language
- Java
- Stars
- 128
- Forks
- 33
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 12
Description
The existing development deployment is essentially a shell script running in a cronjob which tends to be both brittle and opaque. The AMMOS in the Cloud team has been developing a more robust ECS-based deployment using terraform. This meta ticket will track the progress in integrating this work into the existing Aerie developer environment.
### Tasks
- [ ] Standup Aerie terraform deployment (S3 state bucket)
- [ ] Bring infra-as-code into NASA-AMMOS namespace
- [ ] Convert to Continuous Deployment (λ function cron updating ECS tasks)
- [ ] Automate database migrations (λ function running `aerie_db_migration.py`
- [ ] Automate database backups (λ function running pgdump)
- [ ] Update deployment status on GH
Contributor guide
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.