1229181 - Need consumerKey and consumerSecret for new bmo-upstream-merge repo in Treeherder

Status: RESOLVED FIXED

(Tree Management :: Treeherder: API, defect)

Description

[David Lawrence [:dkl]]

Currently we have bmo-master and bmo-development which contain the TaskCluster results from our BMO repo when commits are made (github/mozilla/webtools-bmo-bugzilla). Those are working fine. We need to enable the use of the bmo-upstream-merge repo currently listed in the Treeherder repo list. Dustin, who has enabled the permissions in Taskcluster thinks we may need a consumerKey and consumerSecret specific to the bmo-upstream-merge repo in Treeherder. What do I need to do to obtain those and hand them over to Dustin to allow the results to display properly?

Thanks
dkl

Comment 1

[Ed Morley [:emorley]]

`consumerKey` and `consumerSecret` taken as literal names are nothing that treeherder deals with.

If they are what Taskcluster's configs call Treeherder's hawk credentials of `client_id` and `secret`, then I was under the impression taskcluster was using one set for everything that was submitted via taskcluster?

Comment 2

[David Lawrence [:dkl]]

(In reply to Ed Morley (Away 1st-2nd, 4th Dec) [:emorley] from comment #1)
> `consumerKey` and `consumerSecret` taken as literal names are nothing that
> treeherder deals with.
> 
> If they are what Taskcluster's configs call Treeherder's hawk credentials of
> `client_id` and `secret`, then I was under the impression taskcluster was
> using one set for everything that was submitted via taskcluster?

Thanks for the response. As I understand it, Dustin tried using similar credentials that we currently use for bmo-master and bmo-development but had no success. Dustin, do you have an idea and what else it may be?

dkl

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Nope, I just know there's a file with keys "consumerSecret" and "consumerKey" for each project, and Greg said they had something to do with TreeHerder.  Let's pass the needinfo potato!

Comment 4

[Greg Arndt [:garndt]]

(In reply to Ed Morley (Away 1st-2nd, 4th Dec) [:emorley] from comment #1)
> `consumerKey` and `consumerSecret` taken as literal names are nothing that
> treeherder deals with.
> 
> If they are what Taskcluster's configs call Treeherder's hawk credentials of
> `client_id` and `secret`, then I was under the impression taskcluster was
> using one set for everything that was submitted via taskcluster?

This is because gaia-taskcluster has not been converted to using the new node treeherder client and hawk credentials and is still using per project oauth creds.  Is there a way to get these creds for this particular project with hopes that sometime next week I can get around to updating gaia-taskcluster?

Comment 5

[Ed Morley [:emorley]]

Ah of course that makes sense. It's been a while since I wrote the unlanded PR to remove oaith support that I'd forgotten they were called consumer_key and consumer_secret and didn't know this was using the not migrated gaia-taskcluster library.

I think the old credentials are still being generated for me repos, I'm happy to hand them out on the condition that gaia-taskcluster is updated within the next week or so; I know you've inherited the repo so it's less straightforwards then it would be. Cameron, would you mind doing that for me? :-) 

(It would only apply to new changes moving forwards, but on a related note we're thinking of documenting a "typical EOL timeline" policy, which sets a number of days that submitters have to update to changes in our API; bug 1228304)

Comment 6

[Cameron Dawson [:camd]]

OK, sent those to DKL.

Comment 7

[David Lawrence [:dkl]]

Dustin. I sent them to you in private email. Let me know if you need more to get this set up.

dkl