livepeer / livepeer/test-harness
zombie stackdriver alerting and health checks
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
the test-harness doesn't properly delete the stackdriver uptime checks and alerting once the deployment is deleted, this results in following error
```bash
(node:15690) UnhandledPromiseRejectionWarning: Error: 8 RESOURCE_EXHAUSTED: verifying check config quota. Project 926323785560 has 100 check configs out of 100 allowed. Please delete some checks or request more quota.
```
Edit: the `teardown` function takes care of it, but that only happens when the user uses `./test-harness down`
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
Start by tracing the test-harness deployment deletion path and compare it with the existing teardown function used by ./test-harness down. Reproduce deletion without that command and inspect whether Stackdriver uptime checks and alerting remain. Done means those resources are removed when the deployment is deleted and the quota error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, javascript
- Domain
- cloud, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100