Jeff Mitchell

If I put a print statement in with your line above I see the `--` being passed as a distinct argument: ``` []string{"exec", "-it", "-n", "vault", "vault-1", "--", "sh", "--tls-server-name",...

Marking as bug although when someone gets the chance to dig in it may not end up being a bug in Boundary 🤷

Maybe? It's hard to say. In theory the `boundary connect` call should pass anything after the first `--` straight through. In fact, we have an explicit avoidance of this situation:...

@saada Thanks for the report! This is something we're very interested in but we have not yet thought through the design. There are a few ways we could go: 1....

Thanks for the writeup and pointer to `kconnect`! Going to unpack a few things here: First, I think it would be useful to draw a distinction between a target, a...

There aren't guidelines yet, no. It's just so early :-) You could look at the static host catalog for some initial ideas. But one thing worth cluing you into is...

We don't have a kubernetes target, no. But we have a connect helper for the 'boundary connect' command to make it easy to use the tcp target. See 'boundary connect...

@saada Nobody took me up on that so no discussions happened. At this point the team is fairly slammed and I doubt anything more integrated with Kube than the existing...

We don't assume Go is installed at any specific location -- the `test-ci` target -- which is a newer duplicate of the `test` target and the latter should be removed...

Our preferred/eventual approach for Kubernetes would be to integrate directly with the service catalog, in a fashion similar to the dynamic host catalogs for AWS/Azure that came out in 0.7....