Closed Bug 1583928 Opened 6 years ago Closed 6 years ago

"Deleting" a worker pool requires worker-manager:provider:null-provider

Categories

(Taskcluster :: Services, defect)

Product:
Taskcluster
Component:
Services
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: dustin)

Details

The way the scopes are set up for worker-manager, deleting a worker pool requires worker-manager:provider:null-provider.

I can see a few ways to fix:

  • give everyone this scope (meaning deployments that forget to do so will not allow deletion)
  • special-case deletion in the updateWorkerPool method to not require this scope
  • add a deleteWorkerPool method that acts like updateWorkerPool but doesn't require this scope

Thoughts?

Just having a deleteWorkerPool might make the most sense to someone trying to figure this all out? In a sense they don't care how it is implemented.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.