Replies: 4 comments 1 reply
-
My opinion is that since the new binary is specifically meant for reinstalling the system, and it's no longer a long and arcane podman run bootc invocation (that the user might not know the consequences of), I think we can safely implicitly add But obviously I still think this needs to be discussed |
Beta Was this translation helpful? Give feedback.
-
We can also consider entirely new warnings for the reinstall script, maybe even a y/n prompt at the binary level rather than relying on bootc itself for providing the prompt |
Beta Was this translation helpful? Give feedback.
-
We should also consider how this will interact with the future SSH key / user management related TUI / prompts. If we're gonna prompt the user anyway for the SSH stuff, might as well have something like "WARNING: YOUR SYSTEM WILL BE REINSTALLED followed by <some SSH key related prompt>". As to avoid asking the user too many questions |
Beta Was this translation helpful? Give feedback.
-
IMO, I think the final user input that triggers the reinstall should require something like entering the system's hostname, or typing out "REINSTALL". I'd also like to add a --dry-run flag for devs to prevent accidentally overwriting my system. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Do we want the:
prompt when the user uses our new reinstall binary (BIFROST-610)? Or should we default to
--acknowledge-destructive
?Beta Was this translation helpful? Give feedback.
All reactions