This was discussed in the PR that changed it. As you can see, the original proposed string was SuRe which I opposed. I am personally also simply for [y/N] (the capitalizad N is just to show that that is the default I believe). We compromised and settled on yes/N as @khsrali @GeigerJ2 and @giovannipizzi thought it dangerous to keep just y.

So the idea here was that deleting a computer doesn't only delete the isolated computer. To keep provenance, it also deletes all the connected nodes, so all processes of a user that were run on this computer. So it's an operation that should only be done with great care. Personally, I'd also be fine with [y/N] as that is usually the standard. The fear was that people just quickly pressing through things might accidentally run the operation somewhat unintentional, though, that should be captured with [y/N]. Don't really have a strong opinion on the topic, for me either is fine. Ideally, as always, I'd vouch for consistency.

I'm ok with the original suggestion and generally keeping a consistent style across verdi commands, as long as the default stays N

We thought perhaps using a different response than the usual "y" would make sense to prevent accidental data loss.
As @sphuber said, we compromised to "yes". But if @agoscinski thinks that is confusing regarding standardization, one could replace with "please type: 'confirm deletion' ", like when github asks you when deleting your repo.
This way remain both safe and standard.

I conclude that changing it to [yes/NO] would work for all people. We can still accept N for backwards compatibility.

EDIT: I am sorry for the back and forth but reading now the conversation more carefully and looking at the deletion in other parts of the code. All people were also okay with the [y/N] as long as N stays the default. Since this gives us consistency over the CLI, I conclude to this choice.

Hi can I work on this issue? @agoscinski

Sure!

one could replace with "please type: 'confirm deletion' ", like when github asks you when deleting your repo.

This is a very good idea. ➕ Same thing could be done when deleting a code node or a profile.