1190396 - [PulseGuardian] Permission controls for exchanges

Status: RESOLVED WONTFIX

(Webtools :: Pulse, defect)

Description

[Mark Côté [:mcote]]

Treeherder is going to have use Pulse in a slightly different way from normal:  it will have an exchange to which authorized users can post tasks.  This will require controls in PulseGuardian for granting write permission on a Treeherder exchange to specific Pulse users.

I imagine a view in which a user sees all of their exchanges (see bug 1079523) and can add or remove other Pulse users.  This would create a simple permission string like '^(user1|user2|user3)$'.

Comment 1

[Mark Côté [:mcote]]

Did you eventually decide that there would be a single exchange for events, or that each Treeherder client app would have its own exchange that Treeherder listens to?

Comment 2

[Mark Côté [:mcote]]

Talked to camd and turns out that clients will create their own exchanges, so this is no longer necessary, which is good since it doesn't break our existing model.

Comment 3

[Cameron Dawson [:camd]]

As discussed on vidyo, Treeherder won't need this change.  We create queues for exchanges owned by the other app we ingest data from.