reload: `update` command should require some kind of confirmation

[cottongin]

While writing my own plugin that featured an update command I ran into this since Sopel will run all commands matching a defined command name/alias.

I should think running any sort of git pull command should require an extra step or confirmation, e.g. .update --yes, or something.

sopel/sopel/modules/reload.py

Lines 65 to 67 in 9f5116d

	proc = subprocess.Popen('/usr/bin/git pull',
	stdout=subprocess.PIPE,
	stderr=subprocess.PIPE, shell=True)

To be honest I'm not entirely sure what the benefit of this command is and I'm beginning to align with @Exirel with his disdain for this plugin in general.

[dgw]

If the command becomes .update --yes, then someone will complain that it should be .update --yes --really… But a nonce approach would be reasonable: .update (or the nickname_command equivalent) on its own would send back in a NOTICE something like, "To confirm the update operation, send .update ABAD1DEA" — where ABAD1DEA is randomly generated for that request and stored somewhere in bot.memory until used or replaced (possibly also until some timeout period expires, but that might be unnecessary complication). This works well for dangerous services commands like /ns drop, and we might as well steal the pattern since bot admins are likely already familiar.

Personally, I've been thinking that .update belongs in a separate plugin anyway. All the heavy lifting is handled by the bot object itself, and the commands in reload just wrap those methods with argument checking & error messages (and permissions checks). There's no reason that we can't just split reload into two plugins instead of one when extracting things for 8.x.

[Exirel]

We have two options:

• close, as reload: remove .update command #2416 remove this feature
• keep track of the feature to be extracted into its own plugin

For now, I'll remove the milestone, and @dgw will probably have an opinion on the keep or delete.

[dgw]

Oh, I forgot about this. Totally just close it; I'm not planning to re-add the .update command to reload even if it becomes an external plugin.