Sander van Harmelen b1fdbd7db8 Allow enhanced backends to pass custom exit codes ... In some cases this is needed to keep the UX clean and to make sure any remote exit codes are passed through to the local process. The most obvious example for this is when using the "remote" backend. This backend runs Terraform remotely and stream the output back to the local terminal. When an error occurs during the remote execution, all the needed error information will already be in the streamed output. So if we then return an error ourselves, users will get the same errors twice. By allowing the backend to specify the correct exit code, the UX remains the same while preserving the correct exit codes.		2018-10-05 20:44:12 +02:00
..
test-fixtures	Allow enhanced backends to pass custom exit codes	2018-10-05 20:44:12 +02:00
backend_apply_test.go	Allow enhanced backends to pass custom exit codes	2018-10-05 20:44:12 +02:00
backend_apply.go	Add checks for all flags we currently don’t support	2018-10-05 20:16:34 +02:00
backend_mock.go	Allow enhanced backends to pass custom exit codes	2018-10-05 20:44:12 +02:00
backend_plan_test.go	Allow enhanced backends to pass custom exit codes	2018-10-05 20:44:12 +02:00
backend_plan.go	Add checks for all flags we currently don’t support	2018-10-05 20:16:34 +02:00
backend_state_test.go	backend/remote: add support for state locking	2018-09-10 19:49:53 +02:00
backend_state.go	backend/remote: add support for state locking	2018-09-10 19:49:53 +02:00
backend_test.go	backend/remote: add support for state locking	2018-09-10 19:49:53 +02:00
backend.go	Allow enhanced backends to pass custom exit codes	2018-10-05 20:44:12 +02:00
cli.go	Implement the Enterprise enhanced remote backend	2018-08-03 22:22:55 +02:00
colorize.go	backend/remote: introduce support for -no-color	2018-10-04 18:01:11 +02:00
testing.go	backend/remote: extend mocks and add sentinel tests	2018-09-26 22:34:32 +02:00