Page MenuHomePhabricator

Remove dead "Service Lock" code from Almanac
ClosedPublic

Authored by epriestley on Apr 9 2018, 5:11 PM.
Tags
None
Referenced Files
F19069505: D19316.id.diff
Nov 30 2025, 2:27 PM
F19060138: D19316.id.diff
Nov 29 2025, 8:40 AM
F19054783: D19316.diff
Nov 28 2025, 2:34 PM
F18974614: D19316.id46221.diff
Nov 15 2025, 10:36 PM
F18856010: D19316.diff
Nov 1 2025, 7:36 AM
F18840069: D19316.id46219.diff
Oct 27 2025, 8:50 PM
F18822593: D19316.id46221.diff
Oct 23 2025, 7:37 AM
F18815443: D19316.id.diff
Oct 21 2025, 2:12 AM
Subscribers
None

Details

Summary

Depends on D19315. Ref T13120. Ref T12414. See PHI145. See PHI473. I want to move Almanac services to ModularTransactions but ran into this old piece of dead/unused code along the way.

Long ago, Almanac services could be individually "locked", but this didn't really work out very well. It was replaced by "Can Manage Cluster Services" in D15339 and prior changes, but not all of the old "Lock" code got cleaned up.

I don't expect to restore this feature, so clean it up now.

Test Plan
  • Grepped for AlmanacServiceTransaction::TYPE_LOCK, TYPE_LOCK, etc.
  • Grepped for updateServiceLock(), no callsites.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision is now accepted and ready to land.Apr 9 2018, 5:12 PM
This revision was automatically updated to reflect the committed changes.