Page MenuHomePhabricator

Change bin/storage destroy to be less scary when removing test data
ClosedPublic

Authored by amckinley on Jul 25 2018, 7:08 PM.
Tags
None
Referenced Files
F19836289: D19535.id.diff
Wed, Mar 11, 9:22 AM
F19826123: D19535.diff
Sun, Mar 8, 5:28 PM
F19811896: D19535.diff
Wed, Mar 4, 2:56 AM
F19789742: D19535.diff
Feb 25 2026, 6:35 PM
F19641719: D19535.id.diff
Feb 5 2026, 7:42 PM
F19565913: D19535.id46708.diff
Jan 31 2026, 7:23 PM
F19565912: D19535.id46708.diff
Jan 31 2026, 7:23 PM
F19507779: D19535.id46707.diff
Jan 9 2026, 11:09 PM
Subscribers

Details

Summary

I've pulled up this code probably three different times to make sure that the big scary warning does, in fact, still get printed even when passing --unitest-fixtures to bin/storage destroy. Make the warning message less scary if only removing test data.

Test Plan

Ran with and without --unitest-fixtures and saw expected warnings. After agreeing to warnings, test data was deleted as expected. Did not test bin/storage destroy without --unittest-fixtures.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable