[PulseGuardian] Permission controls for exchanges

RESOLVED WONTFIX

Status

Webtools
Pulse
RESOLVED WONTFIX
3 years ago
3 years ago

People

(Reporter: mcote, Unassigned)

Tracking

(Depends on: 1 bug)

Trunk

Firefox Tracking Flags

(firefox42 affected)

Details

(Reporter)

Description

3 years ago
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)$'.
(Reporter)

Comment 1

3 years ago
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?
Flags: needinfo?(cdawson)
(Reporter)

Comment 2

3 years ago
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.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
(Reporter)

Updated

3 years ago
Flags: needinfo?(cdawson)
As discussed on vidyo, Treeherder won't need this change.  We create queues for exchanges owned by the other app we ingest data from.
You need to log in before you can comment on or make changes to this bug.