The transient ssh subcommand supports an ssh timeout option. This will, as expected, specify the amount of time transient will attempt to ssh in to the VM before giving up. However, if transient ssh is executed immediately after the command that created the VM (like in a script) it will potentially fail immediately saying that there is no VM with the given name. This happens because the ssh timeout only applies once transient knows the ssh address of the VM with the given name (and that information is only available once transient has started the VM).
We should probably extend the ssh-timeout option for the ssh subcommand to also cause transient to wait at least that long for the VM to exist.
The
transient ssh
subcommand supports an ssh timeout option. This will, as expected, specify the amount of timetransient
will attempt to ssh in to the VM before giving up. However, iftransient ssh
is executed immediately after the command that created the VM (like in a script) it will potentially fail immediately saying that there is no VM with the given name. This happens because the ssh timeout only applies oncetransient
knows the ssh address of the VM with the given name (and that information is only available oncetransient
has started the VM).We should probably extend the ssh-timeout option for the
ssh
subcommand to also causetransient
to wait at least that long for the VM to exist.