feat(dashmate)!: confirm a node reset #2160
Open
+45
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
The reset command removes a node data and potentially configuration (if the hard flag is provided). A user must be warned before the command is actually executing.
What was done?
How Has This Been Tested?
Running the reset command locally
Breaking Changes
This change will break any non interactive execution of reset command so now the force flag must be provided to skip the reset confirmation.
Checklist:
For repository code-owners and collaborators only