Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make storage-flush a little safer #70

Closed
prophile opened this issue Aug 29, 2017 · 0 comments
Closed

Make storage-flush a little safer #70

prophile opened this issue Aug 29, 2017 · 0 comments
Labels
Milestone

Comments

@prophile
Copy link
Owner

storage-flush is currently a porcelain command which can immediately destroy the database. Especially after #66 this might be easy to do by accident. It's currently there so that you can empty the database and refill it with an import.

We should:

  1. Add a --flush argument to storage-import,
  2. Mark storage-flush as a plumbing command,
  3. Add a mandatory --force argument to storage-flush.
@prophile prophile added the Easy label Aug 29, 2017
@prophile prophile added this to the 0.5.0 milestone Sep 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant