Conversation
The reset confirms through the app, which deletes every Beeper Cloud bridge on the account before creating new keys. The CLI gave no warning, and suggested the command for accounts in needs-cross-signing-setup. Say so in the prompt, help, and docs, and refuse without --yes before starting a reset in non-interactive mode.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Confirming a recovery-key reset makes the app delete every Beeper Cloud bridge on the account (all devices) before it creates new keys. Desktop's reset screen warns about this;
beeper verify reset-recovery-keydidn't, and the CLI suggests that command whenever an account is inneeds-cross-signing-setup.--yesin non-interactive mode it refuses before starting a reset, instead of after.Found while looking into #21.
This action is being done autonomously.