Change Details

Tested using 3 Phabricator instances (one web, one taskmaster and one storage). The web and taskmaster tiers are directed at the Conduit API of the storage tier. Applied D10400 and D10401 to Phabricator. Applied D10402 to libphutil. Ran `bin/repository lookup-users rTESTe9683b64d3283f0b2d355fdbf231bc918b5ac0ab` and saw the information returned (by making a request to `diffusion.querycommits` as the omnipotent user).

Ran `bin/repository lookup-users rTESTe9683b64d3283f0b2d355fdbf231bc918b5ac0ab --trace` and saw the information returned (by making a request to `diffusion.querycommits` as the omnipotent user, signed with the device key). Mucked with `cluster.addresses` and saw requests rejected.

Tested using 3 Phabricator instances (one web, one taskmaster and one storage).Ran `bin/repository lookup-users rTESTe9683b64d3283f0b2d355fdbf231bc918b5ac0ab --trace` and saw the information returned (by making a request to `diffusion.querycommits` as the omnipotent user, The web and taskmaster tiers are directed at the Conduit API of the storage tier. Applied D10400 and D10401 to Phabricator. Applied D10402 to libphutilsigned with the device key). Ran `bin/repository lookup-users rTESTe9683b64d3283f0b2d355fdbf231bc918b5ac0ab` and saw the information returned (by making a request to `diffusion.querycommits` as the omnipotent user)Mucked with `cluster.addresses` and saw requests rejected.