Separate DB into a separate stack
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, python
- Domain
- cloud, devops, infrastructure
Research direction
Start by reading the repository's deployment setup and the eoapi-cdk constructs it uses, then compare the separate stateful-resources approach in the linked CSDA deployment. Define how the database stack and application stack are named and deployed independently, with cdk deploy $STATELESS-STACK-NAME working for application updates without redeploying the database.
Written by the indexing model from the issue text.
Description
Because deployment updates are much more likely to happen due to updates in the applications (tiler, ingestor, stac api, ...) themselves rather than the database, it would be better to have the latter in a separate, "stateful resources" stack like it's done in CSDA (and then we can say cdk deploy $STATELESS-STACK-NAME).
- Dominant language
- Python
- Stars
- 5
- Forks
- 2
- Avg merge
- 18h 23m
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing 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.
More from developmentseed/eoapi-template
-
Default deploy installs eoapi-cdk 10.3.0, whose STAC runtime fails to import (`No module named 'stac_fastapi.extensions.core.fields'`)Possibly taken @hrodmn claimed this 96 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
developmentseed/eoapi-template#46 · 1 comment ·
All issues in developmentseed/eoapi-template
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
debpalash/VoiceStudio#2624 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Make Catch2 optional when `RDK_BUILD_CPP_TESTS=OFF`Possibly taken @pechersky claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 2 days
-
There are a few redundant calls to `fdesc._setCloseOnExec()`Possibly taken @gudnimg claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day