Enable programmatic invocation of commands without terminal interaction

[kate-goldenring]

The following scenarios require terminal interaction where a flag such as --accept-defaults should be provided for CI scenarios:

• spin cloud deploy for an app with entries in sqlite_databases (you are prompted to choose a DB)
• spin cloud link sqlite when updating a link
• spin cloud sqlite delete you are prompted to confirm your choice to delete the database

[kate-goldenring]

@itowlson am i missing anything here?

[itowlson]

I think that's the lot.

Looking over it, we don't have a very clear policy on confirming destructive actions at the moment (e.g. app delete and sqlite unlink don't confirm, but sqlite delete does), and it's not clear where a good boundary would be (e.g. sqlite execute could be phenomenally destructive but would be a massive pain to have a confirmation on). But if we get a good pattern in for the commands you've listed then that will put us in good stead if we ever add confirmation to any of those. (This is definitely out of scope for this issue of course! I'm just thinking out loud.)

[kate-goldenring]

Looks like we already have the yes flag for deletes. We could add the same to unlink; though, unlink is easy enough to undo that it might not need a prompt