terraform/backend
Martin Atkins b10f058cbb backend/remote: Only load variables if we're going to use them
Some commands don't use variables at all or use them in a way that doesn't
require them to all be fully valid and consistent. For those, we don't
want to fetch variable values from the remote system and try to validate
them because that's wasteful and likely to cause unnecessary error
messages.

Furthermore, the variables endpoint in Terraform Cloud and Enterprise only
works for personal access tokens, so it's important that we don't assume
we can _always_ use it. If we do, then we'll see problems when commands
are run inside Terraform Cloud and Enterprise remote execution contexts,
where the variables map always comes back as empty.
2019-10-18 11:31:19 -07:00
..
atlas Change backend.ValidateConfig to PrepareConfig 2019-02-25 18:37:20 -05:00
init Replace import paths & set UA string where necessary 2019-10-11 22:40:54 +01:00
local Version tools per Go convention under tools.go 2019-10-17 22:23:39 +02:00
remote backend/remote: Only load variables if we're going to use them 2019-10-18 11:31:19 -07:00
remote-state vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
backend.go backend: Allow certain commands to opt out of required variable checks 2019-10-10 10:07:01 -07:00
cli.go backend: Update interface and implementations for new config loader 2018-10-16 18:39:12 -07:00
nil.go Change backend.ValidateConfig to PrepareConfig 2019-02-25 18:37:20 -05:00
nil_test.go
operation_type.go Version tools per Go convention under tools.go 2019-10-17 22:23:39 +02:00
operationtype_string.go stringer: Regenerate files with latest version 2019-05-13 15:34:27 +01:00
testing.go vendor: switch to HCL 2.0 in the HCL repository 2019-10-02 15:10:21 -07:00
unparsed_value.go backend/remote: Report invalid variables only remotely 2019-10-18 11:31:19 -07:00
unparsed_value_test.go backend/local: Handle interactive prompts for variables in UI layer 2019-10-10 10:07:01 -07:00