letsencrypt / letsencrypt/boulder
Nomad- and consul-ify our integration test environment
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
This is the direction that prod is headed. Also, it will let us do things like stop having to specify debug ports, auto-template our configs for multiple copies of a services, and more.
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.
Research direction
The issue does not name files, tests, or entry points. Start by locating the integration test environment and existing service configuration, then determine how Nomad and Consul fit the production direction. Done means the integration environment uses those systems and supports automatic configuration, multiple service copies, and no manually specified debug ports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100