Page MenuHomePhabricator

In "bin/drydock lease", take a JSON "--attributes" so we can accept complex values
ClosedPublic

Authored by epriestley on Oct 24 2018, 2:22 PM.
Tags
None
Referenced Files
F18837069: D19751.diff
Mon, Oct 27, 4:16 AM
F18815688: D19751.id47201.diff
Tue, Oct 21, 3:12 AM
F18815687: D19751.id47183.diff
Tue, Oct 21, 3:12 AM
F18815265: D19751.id.diff
Tue, Oct 21, 1:31 AM
F18815210: D19751.diff
Tue, Oct 21, 1:18 AM
F18808172: D19751.id47201.diff
Sun, Oct 19, 5:16 AM
F18788486: D19751.id.diff
Wed, Oct 15, 5:05 AM
F18701866: D19751.id.diff
Sep 27 2025, 9:32 PM
Subscribers
Restricted Owners Package

Details

Summary

Depends on D19750. See T13210. The bin/drydock lease command makes it easier to request ad-hoc leases, but currently takes lease attributes in the form --attributes x=y,a=b.

This was okay for all leases at the time, but doesn't really work for modern WorkingCopy resources since they take a repositories.map which has a dictionary as a value. You can't specify that with repositories.map=....

Instead, point --attributes at a JSON file or use --attributes - to read from stdin.

Test Plan

Used --attributes with a file and stdin to allocate working copy leases with repositories.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable