phorge-phorge/resources/sql/autopatches/20151010.drydock.auth.2.sql

ALTER TABLE {$NAMESPACE}_drydock.drydock_lease
  ADD authorizingPHID VARBINARY(64) NOT NULL;
Use Drydock authorizations when acquiring leases 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: {F872527} Reviewers: hach-que, chad Reviewed By: chad Maniphest Tasks: T9519 Differential Revision: https://secure.phabricator.com/D14254 2015-10-13 02:02:35 +02:00			`ALTER TABLE {$NAMESPACE}_drydock.drydock_lease`
			`ADD authorizingPHID VARBINARY(64) NOT NULL;`