Closed Bug 1476638 Opened 7 years ago Closed 7 years ago

Turn off CosmoDB

Categories

(Taskcluster :: Operations and Service Requests, task)

Product:
Taskcluster
Component:
Operations and Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

Apparently we've been paying an hourly rate for these since 2015! They appear completely unused: mozilla-circleci-test treeherder-proxy (I think this is the old name for mozilla-taskcluster?) activity logs show no activity, aside from my poking around, in the last 6mo. Brian, do you mind sanity-checking me before I hit "delete"? There appears to be no easy way to disable these without deleting them.
Flags: needinfo?(bstack)
Ah, I found a way -- I'll rotate the access keys. They *are* configured in mozilla-taskcluster's settings in Heroku, but appear to only be used in test/circleci.js, which appears to only be used in m-t's own tests (which don't run in Heroku.. uh..)
Flags: needinfo?(bstack)
seems fine .. let's see what happens.
The unlikely worst-case was that mozilla-taskcluster would stop doing whatever it does. It seems to have continued on doing its thing for 23 hours now (and I restarted the dynos during that time). So, I'm deleting the DBs.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Operations → Operations and Service Requests
You need to log in before you can comment on or make changes to this bug.