opentofu/backend
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
..
atlas Use New() instead of once.Do(b.init) 2018-08-03 11:29:11 +02:00
init Implement the Enterprise enhanced remote backend 2018-08-03 22:22:55 +02:00
legacy Implement the Enterprise enhanced remote backend 2018-08-03 22:22:55 +02:00
local backend/remote: add support for the apply operation 2018-09-22 11:49:42 +02:00
remote Allow enhanced backends to pass custom exit codes 2018-10-05 20:44:12 +02:00
remote-state Fix drift caused from gofmt when running make dev and go 1.11. 2018-09-09 10:18:08 -07:00
backend.go Allow enhanced backends to pass custom exit codes 2018-10-05 20:44:12 +02:00
cli.go Update the backend import names 2018-08-03 11:29:11 +02:00
nil_test.go backend: introduce the backend set of interfaces 2017-01-26 14:33:49 -08:00
nil.go Update Backend interface to latest iteration 2017-02-28 16:07:07 -05:00
operation_type.go backend: introduce the backend set of interfaces 2017-01-26 14:33:49 -08:00
operationtype_string.go Update various files for new version of "stringer" 2017-12-11 13:26:29 -08:00
testing.go Implement the Enterprise enhanced remote backend 2018-08-03 22:22:55 +02:00