You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

James Bardin 2d7dc605a0 get communicator errors from a remote.Cmd ... The remote.Cmd struct could not convey any transport related error to the caller, meaning that interrupted commands would show that they succeeded. Change Cmd.SetExited to accept an exit status, as well as an error to store for the caller. Make the status and error fields internal, require serialized access through the getter methods. Users of remote.Cmd should not check both Cmd.Err() and Cmd.ExitStatus() until after Wait returns. Require communicators to call Cmd.Init before executing the command. This will indicate incorrect usage of the remote.Cmd by causing a panic in SetExitStatus.		8 years ago
..
remote	get communicator errors from a remote.Cmd	8 years ago
shared	provisioners: Allow provisioning over IPv6	10 years ago
ssh	get communicator errors from a remote.Cmd	8 years ago
winrm	get communicator errors from a remote.Cmd	8 years ago
communicator.go	Fix type assertion when loading stored error	8 years ago
communicator_mock.go	get communicator errors from a remote.Cmd	8 years ago
communicator_test.go	add the remote-exec retry function to communicator	8 years ago