Austin McKinley 4dc8e2de56 Add unique constraint to AlmanacInterfaces ... Summary: See discussion in D19379. The 4-tuple of (device, network, address, port) should be unique. Test Plan: Created lots of duplicate interfaces, bound those interfaces to various services, observed migration script clean things up correctly. Reviewers: epriestley Reviewed By: epriestley Subscribers: Korvin, PHID-OPKG-gm6ozazyms6q6i22gyam Differential Revision: https://secure.phabricator.com/D19388		2018-04-19 19:16:50 -07:00
..
application	Clean up some old cluster-ish documentation	2016-04-12 19:14:08 -07:00
capability	Simplify locking of Almanac cluster services	2016-02-25 03:38:39 -08:00
conduit	Provide "almanac.binding.search" and "almanac.binding.edit"	2018-04-11 10:37:38 -07:00
controller	Make various small quality-of-life improvements for Almanac properties	2018-04-11 10:38:41 -07:00
editor	Add unique constraint to AlmanacInterfaces	2018-04-19 19:16:50 -07:00
engineextension	Allow Almanac properties to be set and deleted via Conduit	2018-04-11 10:42:10 -07:00
management	Remove dead "Service Lock" code from Almanac	2018-04-09 11:38:04 -07:00
phid	Rough-in Almanac namespaces	2016-02-22 04:58:35 -08:00
property	Modularize Almanac property transactions	2018-04-11 10:33:18 -07:00
query	Add unique constraint for Almanac network names	2018-04-19 13:41:15 -07:00
servicetype	Allow repository cluster bindings to be marked as not "writable", making them read-only	2018-04-12 16:10:36 -07:00
storage	Add unique constraint to AlmanacInterfaces	2018-04-19 19:16:50 -07:00
typeahead	Store Almanac "service types" instead of "service classes"	2016-02-26 06:21:50 -08:00
util	Add unique constraint for Almanac network names	2018-04-19 13:41:15 -07:00
view	Separate button CSS classes	2017-06-05 20:14:34 +00:00
xaction	Add unique constraint for Almanac network names	2018-04-19 13:41:15 -07:00