89eeaed0a0
* backend/enhanced: start with absolute config path We recently started normalizing the config path before all "command" operations, which was necessary for consistency but had unexpected consequences for remote backend operations, specifically when a vcs root with a working directory are configured. This PR de-normalizes the path back to an absolute path. * Check the error and add a test It turned out all required logic was already present, so I just needed to add a test for this specific use case. |
||
|---|---|---|
| .. | ||
| 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 | ||