Page MenuHomePhabricator

Don't stop on read-only mode for read-only storage workflows
ClosedPublic

Authored by epriestley on May 30 2016, 3:34 PM.
Tags
None
Referenced Files
F15456464: D15987.id38486.diff
Sun, Mar 30, 9:54 AM
F15454306: D15987.id38483.diff
Sat, Mar 29, 5:51 PM
F15453352: D15987.id.diff
Sat, Mar 29, 11:06 AM
F15449470: D15987.diff
Fri, Mar 28, 10:31 AM
F15414656: D15987.id38483.diff
Thu, Mar 20, 1:49 AM
F15413077: D15987.id.diff
Wed, Mar 19, 4:57 PM
F15396314: D15987.id38486.diff
Sun, Mar 16, 1:25 PM
F15336007: D15987.diff
Sat, Mar 8, 6:04 PM
Subscribers
None

Details

Summary

Fixes T11042. Currently, all bin/storage workflows stop if cluster.read-only is set:

$ ./bin/storage adjust
Usage Exception: Phabricator is currently in read-only mode. Use --force to override this mode.

However, some of them (status, dump, databases, etc) are read-only anyway and safe to run. Don't prompt in these cases.

Test Plan
  • Set cluster.read-only to true.
  • Ran bin/storage dump, bin/storage status, etc. No longer received messages.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Don't stop on read-only mode for read-only storage workflows.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.May 30 2016, 3:44 PM
This revision was automatically updated to reflect the committed changes.