No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

If you are telling the Command provider to run an SSH-based command, then jump host/bastion host configuration will be transparent (i.e., if you have a configuration stanza in `~/.ssh/config` it will be used automatically).

Follow up on this; does Pulumi's interactions with `~/.ssh/config`  follow `Include` blocks? I think it's a fairly new feature so unsure if that is respected or not

I believe <@UJBNC99MF> answer is not accurate. The `Command` provider works with the Go SSH Client, which, I believe, do not parse `~/.ssh/config` .
There were two PRs attempting to add bastion configuration in the past: <https://github.com/pulumi/pulumi-command/pulls>

Well that's unfortunate; thanks for the answer Vincent, it looks like this PR adds the functionality in question

<https://github.com/pulumi/pulumi-command/pull/192>