letsencrypt / letsencrypt/boulder
Akamai purge test server: Index purge requests by purged URL
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.8k
- Forks
- 649
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 24
Description
In https://github.com/letsencrypt/boulder/pull/3961#pullrequestreview-180471213 we fix a bug where the number of purge requests to Akamai was not exactly what we expected it to be, because of interference between different test cases. We can probably fix this by having the test server store a map of purged URLs, and let the integration test query that map to ensure that exactly an URL was purged. That way different test cases won't interfere with each other.
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
Start with the Akamai purge test-server and integration-test changes discussed in pull request 3961 and its review. Trace how purge requests are currently counted, then implement URL-indexed tracking so the integration test can verify exactly one purge for its URL without interference from other test cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100