1471316 - [tc-lib-pulse] support getting credentials from tc-pulse

Status: RESOLVED FIXED

(Taskcluster :: Services, enhancement)

Comment 1

[Biboswan Roy]

How is tc-pulse dependent on tc-lib-pulse. How far I get we will hit claimNamespace endpoint with taskcluster credentials and scopes to get a connectionstring. Pls, can you brief it out?

Comment 2

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

That's about right -- the dependency is the other way: tc-lib-pulse should, given appropriate configuration, call pulse.claimNamespace as necessary (re-calling after reclaimAfter) to get its connectionString.

Comment 3

[Biboswan Roy]

tc-client doesn't have the api for tc-pulse. I shall send a PR in tc-client first.

Comment 4

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

Ah, good point.  If that's more complicated than just running the API update tool, let me know.

Comment 5

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

Finished in https://github.com/taskcluster/taskcluster-lib-pulse/pull/7 (after much discussion -- thanks for sticking with that!)

Biboswan, do you want to keep hacking on pulse?  I think the next step is to upgrade a service to use tc-lib-pulse to get its pulse credentials..  I'm also working on bug 1484739 which will put tc-lib-pulse into use in the web frontend.

Comment 6

[Biboswan Roy]

Yeah I would like to

Comment 7

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

I filed a bunch of bugs listed in
  https://bugzilla.mozilla.org/showdependencytree.cgi?id=1436456&hide_resolved=1
if you want to pick one :)

I suspect notify would be a good place to start, as it's just a listener, and if it fails somehow on deployment the impact on Firefox development is small.