Closed
Bug 1407101
Opened 7 years ago
Closed 7 years ago
please add scopes to moz-tree:level:1
Categories
(Taskcluster :: Operations and Service Requests, task)
Taskcluster
Operations and Service Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozilla, Assigned: garndt)
References
Details
Please add these scopes to moz-tree:level:1 :
project:releng:balrog:channel:*
project:releng:balrog:server:dep
project:releng:beetmover:action:*
project:releng:beetmover:bucket:dep
project:releng:googleplay:dep
We're essentially following signing, where all the format scopes are allowed, but we restrict by key type (release / nightly / dep). So the balrog channels and beetmover actions will all be allowed, but only against staging servers + buckets. Right now the googleplay:dep scope will throw an exception, but we can add a dry-run with that scope.
Reporter | ||
Comment 1•7 years ago
|
||
Could we also add
project:releng:buildbot-bridge:*
queue:route:index.releases.v1.maple.*
to maple?
Assignee | ||
Comment 2•7 years ago
|
||
Scopes in the description have been added to moz-tree:level:1
https://tools.taskcluster.net/auth/roles/moz-tree%3Alevel%3A1
Assignee | ||
Comment 3•7 years ago
|
||
For now, I have manually updated maple to have those two scopes.
In the future, we'll find a way of defining project level scopes that tc-admin can use when creating the role.
Please reopen if there is an issue.
Assignee: nobody → garndt
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•7 years ago
|
||
Thanks!
Updated•6 years ago
|
Component: Service Request → Operations and Service Requests
You need to log in
before you can comment on or make changes to this bug.
Description
•