a8d01e3940
The remote backend uses backend.ParseVariableValues locally only to decide if the user seems to be trying to use -var or -var-file options locally, since those are not supported for the remote backend. Other than detecting those, we don't actually have any need to use the results of backend.ParseVariableValues, and so it's better for us to ignore any errors it produces itself and prefer to just send a potentially-invalid request to the remote system and let the remote system be responsible for validating it. This then avoids issues caused by the fact that when remote operations are in use the local system does not have all of the required context: it can't see which environment variables will be set in the remote execution context nor which variables the remote system will set using its own generated -var-file based on the workspace stored variables. |
||
|---|---|---|
| .. | ||
| testdata | ||
| backend.go | ||
| backend_apply.go | ||
| backend_apply_test.go | ||
| backend_common.go | ||
| backend_context.go | ||
| backend_mock.go | ||
| backend_plan.go | ||
| backend_plan_test.go | ||
| backend_state.go | ||
| backend_state_test.go | ||
| backend_test.go | ||
| cli.go | ||
| colorize.go | ||
| remote_test.go | ||
| testing.go | ||