Closed Bug 1447971 Opened 8 years ago Closed 8 years ago

Please add queue:get-artifact:project/gecko/android-ndk/* scope to mozilla-ldap/bli@mozilla.com/fennec

Categories

(Taskcluster :: Operations and Service Requests, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Unassigned)

Details

No description provided.
If I add that scope to that clientId, the clientId will be automatically disabled since bli does not have that scope. Is there and LDAP group of people that need access to this particular artifact name prefix?
How is it that she has the android-sdk/* scope? The ndk scope should be added to the same place I guess.
https://tools.taskcluster.net/auth/roles/moz-tree:level:1:* has queue:get-artifact:project/gecko/android-* so if one exists, then the other should, too. I don't see anything about android-sdk/* specifically.
(In reply to Dustin J. Mitchell [:dustin] pronoun: he from comment #3) > https://tools.taskcluster.net/auth/roles/moz-tree:level:1:* has > queue:get-artifact:project/gecko/android-* so if one exists, then the other > should, too. I don't see anything about android-sdk/* specifically. I don't know what have happened to the old client 'mozilla-ldap/bli@mozilla.com' and 'mozilla-ldap/bli@mozilla.com/fennec'. As far as I can recall, when I visited https://tools.taskcluster.net/credentials, ClientId was 'mozilla-ldap/bli@mozilla.com', but now it's 'mozilla-auth0/ad|Mozilla-LDAP|bli'. Since 'mozilla-auth0/ad|Mozilla-LDAP|bli' has queue:get-artifact:project/gecko/android-*, I created a new client under 'mozilla-auth0/ad|Mozilla-LDAP|bli', and the queue:get-artifact:project/gecko/android-ndk/* scope could be added.
Sounds like you fixed it up!
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: Service Request → Operations and Service Requests
You need to log in before you can comment on or make changes to this bug.