[CLI] Delete commands should support multiple targets

[tjtelan]

We should allow the fluvio [topic, smart-module, connectors, etc...] delete to accept multiple names.

The intended outcome is that each of the names listed get deleted, as opposed to 1 command per resource.

Unless there are strong feelings for a different default behavior, in the event of an error, we should return an error to stderr, and exit on the first encounter. But if we provide a flag, something like --force or --continue-on-error, then cycle through all the names.

[ajhunyady]

What if a SmartModule is referenced in a Connector? I believe, we should prevent it from being deleted, otherwise, the connector may unexpectedly stop working.

[tjtelan]

@ajhunyady I don't think it is the CLI's responsibility to check on the SmartModules in use by connectors. If that workflow is available now, then we should prevent it on the cluster while it is servicing the request.

The point of this issue is more about making it easier to send multiple requests from the CLI with a single command, by looping over a list of names instead of exactly one.

[tomuxmon]

Hey, according to clap you can just Use Vec<T> and add required = true to disallow zero-length Vec.
Would look something like this:

#[derive(Debug, Parser)]
pub struct DeleteTopicOpt {
    /// The name of the Topic to delete
    #[clap(value_name = "name", required = true)]
    topics: Vec<String>,
}

impl DeleteTopicOpt {
    pub async fn process(self, fluvio: &Fluvio) -> Result<()> {
        let admin = fluvio.admin().await;
        for topic in self.topics.iter() {
            debug!("deleting topic: {}", topic);
            admin.delete::<TopicSpec, _>(topic).await?;
            println!("topic \"{}\" deleted", topic);
        }
        Ok(())
    }
}

I can prepare a pull request and see what it looks like.

[sehz]

done