Page MenuHomePhabricator

Expose Drydock leases via Conduit

Authored by epriestley on Sep 24 2016, 7:19 AM.
Referenced Files
Unknown Object (File)
Wed, Jan 18, 10:08 PM
Unknown Object (File)
Mon, Jan 16, 6:57 AM
Unknown Object (File)
Dec 24 2022, 11:19 AM
Unknown Object (File)
Dec 13 2022, 8:53 AM
Unknown Object (File)
Nov 23 2022, 7:39 AM
Unknown Object (File)
Nov 23 2022, 7:39 AM
Unknown Object (File)
Nov 23 2022, 7:39 AM
Unknown Object (File)
Nov 23 2022, 7:38 AM
Restricted Owners Package



See T13212 for some context and discussion on this being revived.
See T11694 for original context.

Add a query constraint for lease owners and implement the conduit search method for Drydock leases.

Ref T11694. Fixes T13212.

Test Plan
  • Called the API method from conduit and browsed lease queries from the UI.
  • Used the new "ownerPHIDs" constraint via API console.

Screen Shot 2018-10-25 at 4.45.22 AM.png (1×2 px, 207 KB)

Diff Detail

rP Phabricator
Lint Not Applicable
Tests Not Applicable

Event Timeline

yelirekim retitled this revision from to Expose Drydock leases via Conduit.
yelirekim updated this object.
yelirekim edited the test plan for this revision. (Show Details)
yelirekim edited edge metadata.

Don't yet presume that users will be lease owners


This isn't a Datasource because owners are a weird mishmash of different object types, I assume? Seems OK to me to let users search by owner, but I think pretty much anything can own a lease right now?


What's your use case for reading attributes? I'm not sure we should dump them verbatim -- they may conceivably contain internal data or keys, and I think their structure is somewhat in flux, and they're probably not the most-preferred format for consumption. If possible, clients probably shouldn't be relying on raw attributes.

If this is for completeness, maybe omit it?

If this is for a particular purpose, maybe we can find a better way to expose the data that's more client-consumable?


Yeah, initially I had this as a user facing typeahead that accepted people as it's datasource, was thinking of combining build steps and people into one datasource, but then you would have to be able to search build steps by name, etc etc.


Internally we display like, what version of the workspace you have checked out from the CLI when you're looking at your leases, or the hostname of the machine if you have a machine lease.

We can just implement it as a search attachment when reintegrating with upstream, probably would tend to agree with you more that it needs some work before being exposed over the API.

epriestley added a reviewer: yelirekim.

See T13212. I'm going to bring everything except attributes upstream, modulo one or two tiny tweaks.

My version of this is substantially identical, but note that until is now an integer or null and may previously have been a string, possibly including the empty string.

epriestley edited the test plan for this revision. (Show Details)
  • Remove attributes.
  • Add ownerPHID as an alias.
  • Be a little stricter about until types.
Owners added a subscriber: Restricted Owners Package.Oct 25 2018, 11:46 AM
This revision is now accepted and ready to land.Oct 26 2018, 1:43 AM
This revision was automatically updated to reflect the committed changes.