Closed
Bug 1219944
Opened 10 years ago
Closed 9 years ago
document conventions in docs.tc.net
Categories
(Taskcluster :: Services, defect)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
We are starting to establish some conventions and/or best practices.
The most recent was that we can avoid scope escalation by requiring that the caller actually possess a role when modifying the thing that will get that role. So for example, to edit hook `hgi/hi`, you must have scope `assume:hook-id:hgi/hi`.
Assignee | ||
Comment 1•9 years ago
|
||
Assignee | ||
Updated•9 years ago
|
Component: General → Documentation
Assignee | ||
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Component: Documentation → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•