Closed
Bug 1220750
Opened 9 years ago
Closed 9 years ago
Assign each worker an appropriate role, remove wt.scopes
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1217088
People
(Reporter: dustin, Unassigned)
Details
Now that we have roles, the provisioner should just assign a well-known role to each workerType, rather than allowing an open list of scopes.
Those roles should be:
assume:worker-type:aws-provisioner-v1/<workerType>
assume:worker-id:<region>/<instanceId>
This will not affect the scopes provided to workers -- each workerType's scopes are currently set as described (well, with `*` for <region>/<instanceId>). So this is just making that configuration automatic.
Reporter | ||
Comment 1•9 years ago
|
||
So specific steps for this bug:
- remove `scopes` from the workerType schemata
- when spawning a worker, use the roles given in comment 0 instead of `scopes`.
Comment 2•9 years ago
|
||
See bug 1217088, almost the same...
Reporter | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: AWS-Provisioner → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•