@fyrchik Should we add some comments here? The batching happens implicitly, so...
I am sure the error check must NOT be ignored here: we'll never figure out if TreeApply is failed in Go
params 3, 4 seems a little bit inconvinient :). 3 is enough (keeping a room for grpc.DialOption doesn't make big profit)
There are many ways to check if an object exists. But for me it's more logically correct to check the error from deletion because I check concurrent deletes
It is not necessary to get container
I fixed this but anyway getting the container doesn't seem to burden the iteration :)
Thanks! Forgot to fix after changes. Fixed
I moved this option to list command for comfortable usage for everyone and removed search
Can we check first condition at the beginning of searchContainer() or earlier? Maybe also will be useful to search by the pat of the name?
Glancing at bucket names like `9d6c424a-7a69-4662-836…