Ted Teng

> For the temporary testing, those are good 👍 The same can apply for `kubectx`, `terraform` and `kubectl` Thanks, @dansible . for those subcommands go files it invokes the different...

> If I understand it correctly here the image https://github.com/gardener/ops-toolbelt > Only the credentials part is missed. yes as ops-toolbelt is one of the options, in a container to git...

- [x] logs_test.go as https://github.com/gardener/gardenctl/pull/425 coverd

- [x] kubectl.go - [x] kubectx.go - [x] terraform.go will cover in https://github.com/gardener/gardenctl/issues/447 - [x] ssh_test.go cover in https://github.com/gardener/gardenctl/pull/440 and https://github.com/gardener/gardenctl/issues/447

yes also observe this in https://github.com/gardener/gardenctl/pull/404#discussion_r514777299. the `checkError` not return and exit after invoked, haven't got an idea of how to improve it at that time.

https://github.com/gardener/gardenctl/pull/404/files

a heads-up. one scenario I meet today. If `gardenctl` is not hard coded and replaced by `os.Args[0]`. it will trigger the diff error when `make gen-markdown && make test` because...

per information https://github.com/gardener/gardenctl-v2/issues/120 and https://github.com/gardener/gardenctl-v2/issues/109, I don't know which one is best. either display required information after targeting the shoot cluster `gardenctl target --project xx --project xx --shoot xx`, or...

if I understand correctly the implementation will not be in Gardenctl repo or Bastions repo. it will be enhanced from gardener/gardener? not clear if new implementation comes from gardener/gardener side?...

History fuzzy feature read for review in PR https://github.com/gardener/gardenctl-v2/pull/162