Skip to content

Conversation

@dnwiebe
Copy link
Collaborator

@dnwiebe dnwiebe commented Aug 3, 2025

Note

Medium Risk
Changes key-selection behavior at startup by allowing forced regeneration or strict reuse of the persisted public key; misconfiguration (especially without --db-password) can now hard-fail startup.

Overview
Adds a new --new-public-key {on|off} configuration option (CLI/env/config/setup UI) to control whether the Node reuses its previously persisted public key or generates and persists a fresh one on startup.

Introduces a shared OnOff clap enum and reuses it for --scans, updates bootstrapping/config parsing to plumb the new flag through (BootstrapperConfig.new_public_key_opt), and adds validation/panic paths when off is requested but reuse is impossible (no DB password or no stored key).

Updates setup reporting/test fixtures to include the new parameter, tightens a test assertion message, adds missing EnvironmentGuard setup in config dumper tests, and ignores JetBrains Copilot files in .gitignore.

Written by Cursor Bugbot for commit 31c0f59. This will update automatically on new commits. Configure here.

@dnwiebe dnwiebe changed the base branch from GH-622-review2 to master September 1, 2025 11:35
@kauri-hero kauri-hero linked an issue Sep 5, 2025 that may be closed by this pull request
cursor[bot]

This comment was marked as outdated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enable Changing Public Key

4 participants