Page MenuHomePhabricator

Allow Almanac services to be locked
ClosedPublic

Authored by epriestley on Dec 18 2014, 1:02 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Apr 10, 6:26 PM
Unknown Object (File)
Tue, Apr 9, 3:02 AM
Unknown Object (File)
Mon, Apr 1, 7:44 AM
Unknown Object (File)
Mar 10 2024, 6:17 AM
Unknown Object (File)
Mar 7 2024, 7:29 PM
Unknown Object (File)
Feb 14 2024, 9:52 AM
Unknown Object (File)
Feb 13 2024, 9:29 AM
Unknown Object (File)
Jan 30 2024, 1:31 PM
Subscribers

Details

Summary

Fixes T6741. This allows Almanac services to be locked from the CLI. Locked services (and their bindings, interfaces and devices) can not be edited. This serves two similar use cases:

  • For normal installs, you can protect cluster configuration from an attacker who compromises an account (or generally harden services which are intended to be difficult to edit).
  • For Phacility, we can lock externally-managed instance cluster configuration without having to pull any spooky tricks.
Test Plan
  • Locked and unlocked services.
  • Verified locking a service locks connected properties, bindings, binding properties, interfaces, devices, and device properties.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Allow Almanac services to be locked.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
btrahan added inline comments.
src/applications/almanac/servicetype/AlmanacClusterServiceType.php
30–31

"See %s for more information." maybe?

This revision is now accepted and ready to land.Dec 18 2014, 9:30 PM
This revision was automatically updated to reflect the committed changes.