Page MenuHomePhabricator

Use Drydock authorizations when acquiring leases
ClosedPublic

Authored by epriestley on Oct 12 2015, 1:26 PM.
Tags
None
Referenced Files
F13181595: D14254.id34416.diff
Thu, May 9, 1:28 PM
Unknown Object (File)
Tue, May 7, 7:25 AM
Unknown Object (File)
Fri, May 3, 6:13 AM
Unknown Object (File)
Thu, Apr 25, 1:03 AM
Unknown Object (File)
Apr 8 2024, 12:13 PM
Unknown Object (File)
Mar 10 2024, 3:46 PM
Unknown Object (File)
Mar 4 2024, 4:38 PM
Unknown Object (File)
Jan 24 2024, 4:52 AM
Subscribers
None

Details

Summary

Ref T9519. When acquiring leases on resources:

  • Only consider resources created by authorized blueprints.
  • Only consider authorized blueprints when creating new resources.
  • Fail with a tailored error if no blueprints are allowed.
  • Fail with a tailored error if missing authorizations are causing acquisition failure.

One somewhat-substantial issue with this is that it's pretty hard to figure out from the Harbormaster side. Specifically, the Build step UI does not show field value anywhere, so the presence of unapproved blueprints is not communicated. This is much more clear in Drydock. I'll plan to address this in future changes to Harbormaster, since there are other related/similar issues anyway.

Test Plan

Screen Shot 2015-10-12 at 5.43.47 AM.png (272×1 px, 51 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Use Drydock authorizations when acquiring leases.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added reviewers: chad, hach-que.
chad edited edge metadata.
This revision is now accepted and ready to land.Oct 12 2015, 2:08 PM
This revision was automatically updated to reflect the committed changes.