Page MenuHomePhabricator

Apply namespace locking rules in Almanac
ClosedPublic

Authored by epriestley on Feb 21 2016, 10:43 PM.

Details

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.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Apply namespace locking rules in Almanac.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Slightly clearer documentation.
chad edited edge metadata.
This revision is now accepted and ready to land.Feb 22 2016, 6:47 AM
This revision was automatically updated to reflect the committed changes.