New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 887966 link

Starred by 1 user
Status: Verified
Owner:
nicolaso@chromium.org
Closed: Sep 21
Cc:
lafo...@chromium.org
rsesek@chromium.org
█ pras...@chromium.org
█ benhenry@chromium.org
mmoss@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

Add a "reverse who" to OmahaProxy

Project Member Reported by nicolaso@chromium.org, Sep 21 
OmahaProxy has a `/who' page [1] for looking up @google.com accounts given an @chromium.org username.

But there's currently no way to map the other way (@google.com => @chromium.org), it seems...

We could add a new page for the reverse mapping, or add support for this on the existing `/who' page.

FWIW I can come up with a patch for this myself.

[1] https://omahaproxy.appspot.com/who

Comment 1 by mmoss@chromium.org, Sep 21

Cc: benhenry@chromium.org pras...@chromium.org
This type of thing arguably doesn't belong in omahaproxy (despite existing precedent), since it has nothing to do with, you know, proxying omaha data. There are efforts underway to provide this type of information in other, more logical settings, like chromiumdash. +benhenry, prasadv

Comment 2 by nicolaso@chromium.org, Sep 21 

>doesn't belong in omahaproxy

I understand that, but perhaps we can have this feature here temporarily, until we can move it to chromiumdash?

We can also file a separate bug to migrate the functionality to chromiumdash (and make omahaproxy.appspot.com/who 301-redirect to it) as a second step.

Comment 3 by mmoss@chromium.org, Sep 21 

Yeah, I just don't want to waste effort making more of a mess of omahaproxy if it would be easy enough to implement in chromiumdash in the first place, but prasadv would be a better judge of that.
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 21 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/infra/infra_internal/+/4c4ad5ddf418c22ba2c956c6be4fb17f599c2f98

commit 4c4ad5ddf418c22ba2c956c6be4fb17f599c2f98
Author: Nicolas Ouellet-payeur <nicolaso@google.com>
Date: Fri Sep 21 17:00:16 2018

Comment 5 by nicolaso@chromium.org, Sep 21

Status: Verified (was: Assigned)
►

Sign in to add a comment