keygen_exists
Diagnostic `nanook::cli::keygen_exists`
Summary
identity file already exists at `{0}`
Help
pass --force to overwrite, or pick a different --path
Details
When this fires
nanook keygen was asked to write an identity at a path where one already exists (either the private key or the matching .pub), and you didn't pass --force. We refuse to overwrite by default since clobbering a key would lock you out of any admin endpoint that trusts it.
What to check
If you really want a fresh key at the same path, take a backup first then pass --force:
Or pick a different path:
Update [admin].authorized with the new .pub after rotating.