Hey all Quick question on the UX around the `kube...
# 💻|contributing
b
Hey all Quick question on the UX around the
kubernetes-exec
type. I love this feature and I think it'll be very useful. But I'm not entirely sure what exactly the intended workflow is. Currently I tend to run something like
garden exec api /bin/sh
. This gives my a shell into one of my services and from there I run integ tests. Usually focused, a single test at a time. So in the shell I'll run
npm test -g "the-test-i-am-focusing-on"
Does this the
kubernetes-exec
type replace this workflow? If so, can I avoid having to duplicate all the test specs such that there's not a corresponding
kubernetes-exec
type for all my tests? E.g. via something like
garden test my-test --exec
? And similarly
garden test my-test --exec -- -g "the-test-i-am-focusing-on"
?