terraform/backend/remote/test-fixtures
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
..
apply backend/remote: extend mocks and add sentinel tests 2018-09-26 22:34:32 +02:00
apply-destroy backend/remote: extend mocks and add sentinel tests 2018-09-26 22:34:32 +02:00
apply-no-changes backend/remote: extend mocks and add apply tests 2018-09-26 21:35:41 +02:00
apply-policy-hard-failed backend/remote: extend mocks and add sentinel tests 2018-09-26 22:34:32 +02:00
apply-policy-passed Revert "Merge pull request #18980 from hashicorp/f-policy-output" 2018-10-04 23:03:40 +02:00
apply-policy-soft-failed backend/remote: extend mocks and add sentinel tests 2018-09-26 22:34:32 +02:00
apply-with-error Allow enhanced backends to pass custom exit codes 2018-10-05 20:44:12 +02:00
plan backend/remote: extend mocks and add apply tests 2018-09-26 21:35:41 +02:00
plan-with-error Allow enhanced backends to pass custom exit codes 2018-10-05 20:44:12 +02:00
plan-with-working-directory/terraform backend/remote: extend mocks and add apply tests 2018-09-26 21:35:41 +02:00