Kristin Laemmert 89eeaed0a0 [WIP] backend/enhanced: start with absolute configuration path (#22096) ...

* 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.

2019-07-17 08:39:37 -04:00

..

atlas

Change backend.ValidateConfig to PrepareConfig

2019-02-25 18:37:20 -05:00

init

Add Alibaba Cloud backend OSS with lock

2019-04-11 07:06:43 +08:00

local

Standardise directory name for test data

2019-06-30 10:16:15 +02:00

remote

[WIP] backend/enhanced: start with absolute configuration path (#22096)

2019-07-17 08:39:37 -04:00

remote-state

Merge pull request #21739 from hasheddan/s3-backend-comment-typo

2019-07-12 14:01:26 -04:00

backend.go

Change backend.ValidateConfig to PrepareConfig

2019-02-25 18:37:20 -05:00

cli.go

backend: Update interface and implementations for new config loader

2018-10-16 18:39:12 -07:00

nil_test.go

backend: introduce the backend set of interfaces

2017-01-26 14:33:49 -08:00

nil.go

Change backend.ValidateConfig to PrepareConfig

2019-02-25 18:37:20 -05:00

operation_type.go

backend: introduce the backend set of interfaces

2017-01-26 14:33:49 -08:00

operationtype_string.go

stringer: Regenerate files with latest version

2019-05-13 15:34:27 +01:00

testing.go

Change backend.ValidateConfig to PrepareConfig

2019-02-25 18:37:20 -05:00

unparsed_value_test.go

backend: Cap number of "undeclared variable" warnings at four

2019-03-05 15:42:08 -08:00

unparsed_value.go

backend: Cap number of "undeclared variable" warnings at four

2019-03-05 15:42:08 -08:00