ocurrent / ocurrent/ocurrent-deployer
AWS deployments should have a test deployment stage
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 24
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
Before pushing to AWS for opam.ocaml.org and ocaml.org, the container should be tested on a non-live service to ensure that it starts. If that stage fails, then the deployment itself doesn't proceed, and the website(s) remain at the previous deployment (with the issue picked up on the firehose).
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
No files, tests, or entry points are named. Trace the existing AWS deployment flow for opam.ocaml.org and ocaml.org, identify where the live deployment occurs, and add a non-live startup check before it. Done means a failed test deployment blocks promotion, preserves the previous website deployment, and reports the failure on the firehose.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, ocaml
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100