Yevgeniy Firsov

Named parameters alllows more flexible usage of utility, for example: `./st_client add -d db1 -t t1 -c c1 -s svc1 -i mysql -o kafka -f avro -v 1` instead of...

Both [replication](https://github.com/siddontang/go-mysql) and [snapshot](https://github.com/go-sql-driver/mysql) libraries support configuring custom TLS connection. We need to add support of custom TLS configuration per Storagtapper instance and per individual cluster, table.

Currently, resolvers are used to resolve source connection information only. For output destination configuration is hard-coded in config files. So it's difficult to configure output destinations per stream.

In state connection resolver, was implemented to resolve MySQL connection details specifically. It needs to be extended to be able to resolve Kafka, HDFS, S3 connetion details.

Currently we are using v1 branch of a fork of https://github.com/colinmarc/hdfs library. The fork includes reliability fixes, but v1 branch doesn't have Kerberos support. We need to port reliability fixes...

Having stdout output and configuration through command line options will allow to use Storagetapper as a command line utility.

Add ability to exclude and include methods

3

It would be useful to allow to exclude some methods of the original struct from generated interface or have only explicitly specified methods be included in the the interface.