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
F18768578: D19535.diff
Wed, Oct 8, 4:19 AM
F18755837: D19535.id46707.diff
Sun, Oct 5, 7:40 AM
F18720358: D19535.id.diff
Mon, Sep 29, 6:42 PM
F18705875: D19535.diff
Sun, Sep 28, 1:40 PM
F18625873: D19535.id46708.diff
Sep 15 2025, 11:49 PM
F18509699: D19535.id.diff
Sep 5 2025, 3:33 AM
F18503007: D19535.diff
Sep 4 2025, 10:48 PM
F18217113: D19535.id46708.diff
Aug 19 2025, 8:27 AM
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