epriestley 411331469a Apply namespace locking rules in Almanac ... Summary: Ref T10246. Ref T6741. When you have a namespace like "phacility.net", require users creating services and devices within it to have edit permission on the namespace. This primarily allows us to lock down future device names in the cluster, so instances can't break themselves once they get access to Almanac. Test Plan: - Configured a `phacility.net` namespace, locked myself out of it. - Could not create new `stuff.phacility.net` services/devices. - Could still edit existing devices I had permission for. - Configured a `free.phacility.net` namespace with more liberal policies. - Could create `me.free.phacility.net`. - Still could not create `other.phacility.net`. Reviewers: chad Reviewed By: chad Maniphest Tasks: T6741, T10246 Differential Revision: https://secure.phabricator.com/D15325		2016-02-22 04:58:53 -08:00
..
AlmanacBindingEditor.php	Add AlmanacBinding, to bind a service to an interface	2014-10-27 13:39:36 -07:00
AlmanacDeviceEditor.php	Apply namespace locking rules in Almanac	2016-02-22 04:58:53 -08:00
AlmanacNamespaceEditEngine.php	Rough-in Almanac namespaces	2016-02-22 04:58:35 -08:00
AlmanacNamespaceEditor.php	Apply namespace locking rules in Almanac	2016-02-22 04:58:53 -08:00
AlmanacNetworkEditor.php	Allow Almanac namespaces to be searched by ngram index	2016-02-22 04:58:18 -08:00
AlmanacServiceEditor.php	Apply namespace locking rules in Almanac	2016-02-22 04:58:53 -08:00