Closed
Bug 1325657
Opened 8 years ago
Closed 7 years ago
pulse_actions - Remove powerful scopes once treeherder handles tc creds
Categories
(Testing :: General, defect)
Testing
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bstack, Assigned: bstack)
References
Details
No description provided.
Comment 1•8 years ago
|
||
Excited to see this filed! Thanks bstack
Comment 2•8 years ago
|
||
Moving to Testing::General, since that's where I see most of the other pulse_actions bugs are (since this doesn't involve changes to treeherder directly). I have permissions to create Bugzilla components, if you wanted one added for pulse_actions? :-)
Component: Treeherder → General
Product: Tree Management → Testing
Summary: Remove powerful scopes from pulse_actions once treeherder handles tc creds → pulse_actions - Remove powerful scopes once treeherder handles tc creds
Version: --- → unspecified
Assignee | ||
Updated•8 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•8 years ago
|
||
This bug was created because we initially had to give pulse_actions ["queue:route:tc-treeherder.v2.*" "queue:route:tc-treeherder-stage.v2.*"] in order to backfill. I went today to remove those scopes since all of this happens from inside treeherder ui now, but pulse_actions now has the scopes:
assume:repo:hg.mozilla.org/*
auth:aws-s3:read-write:tc-gp-public-31d/ateam/pulse-action-dev/*
queue:create-task:*
queue:define-task:*
scheduler:create-task-graph
scheduler:extend-task-graph
(link: https://tools.taskcluster.net/auth/clients/#project%252fateam%252fpulse_actions)
This is far greater than we added for the backfilling tasks and I'm not sure how to proceed in rolling back these permissions from the perspective of this bug. I assume these scopes were needed for some other thing that pulse_actions does. Unfortunately, we don't know when these were changed or who changed them.
Comment 4•7 years ago
|
||
Shutting pulse_actions off (see bug 1379172).
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•