Closed
Bug 1384676
Opened 7 years ago
Closed 7 years ago
Remove un-namespaced role "staging-provisioner"
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
Details
https://tools.taskcluster.net/auth/roles/staging-provisioner Is this used? If so, please rename it to project:taskcluster:provisioner-testing
Flags: needinfo?(jhford)
Comment 1•7 years ago
|
||
It is in use for the staging provisioner. It is not for testing. I'm not sure when I'll have a chance to do this, but the relevant heroku app is here: https://dashboard.heroku.com/apps/provisioner-staging
Flags: needinfo?(jhford)
Assignee | ||
Comment 2•7 years ago
|
||
OK, thanks, I added a new one and removed the old: https://tools.taskcluster.net/auth/roles/project%3Ataskcluster%3Aaws-provisioner-staging I changed the staging client to refer to the new group.
Assignee: nobody → dustin
Assignee | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•7 years ago
|
||
By the way, there's a namespaces document -- https://docs.taskcluster.net/manual/design/namespaces -- that gives guidance on naming things like roles, clients, scopes, artifacts, etc.
Updated•5 years ago
|
Component: Authentication → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•