Consider supporting multiple NAMEs on some commands

[duglin]

In what area(s)?

Classifications:
/kind feature
/kind proposal

Describe the feature:

It would be nice if some commands supported multiple resource names to make life easier for people. For example, I was cleaning up my env and I tried this:

$ kn service delete echo helloworld foo
requires the service name.

and it died because it wasn't expecting more than one service name. It would be nice if we could support multiple NAMEs on certain commands where it makes sense.

It's also kind of an odd error message right now. I would have expected something more like only one service name is allowed, not a message implying I didn't specify any at all.

[navidshaikh]

This is needed, I have to clean my dev environment, it needed multiple kn service delete commands.

I think we should implement this for kn service delete as well as kn revision delete
along with say --all option to delete all the services or revisions in current namespace.

It's also kind of an odd error message right now. I would have expected something more like only one service name is allowed, not a message implying I didn't specify any at all.

This is bug.

[daisy-ycguo]

/assign

[wslyln]

@daisy-ycguo just wanted to double check you're not working on multiple names on revision delete

I'd be up to work on it revision delete and trigger delete.

I checked the rest of the commands in kn and it doesn't seem like there are any others that multiple arguments really make sense. (I guess there might be a case of updating multiple services at a time, though it'd be pretty tricky)

[wslyln]

/assign

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[duglin]

/remove-lifecycle stale
@daisy-ycguo @wslyln were one of you going to work on this?

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.