terraform/backend
Alisdair McDiarmid 619c6727ef backend/remote: No version check for operations
Terraform remote version conflicts are not a concern for operations. We
are in one of three states:

- Running remotely, in which case the local version is irrelevant;
- Workspace configured for local operations, in which case the remote
  version is meaningless;
- Forcing local operations with a remote backend, which should only
  happen in the Terraform Cloud worker, in which case the Terraform
  versions by definition match.

This commit therefore disables the version check for operations (plan
and apply), which has the consequence of disabling it in Terraform Cloud
and Enterprise runs. In turn this enables Terraform Enterprise runs with
bundles which have a version that doesn't exactly match the bundled
Terraform version.
2020-12-17 12:58:38 -05:00
..
init backend: remove deprecated atlas backend 2020-10-26 14:05:18 -04:00
local set SkipRefresh for plan and apply 2020-12-10 09:47:13 -05:00
remote backend/remote: No version check for operations 2020-12-17 12:58:38 -05:00
remote-state update remote state to use legacy types 2020-12-02 12:16:35 -05:00
backend.go helper: deprecate pathorcontents 2020-10-08 08:42:16 -04:00
backend_test.go helper: deprecate pathorcontents 2020-10-08 08:42:16 -04:00
cli.go backend: Update interface and implementations for new config loader 2018-10-16 18:39:12 -07:00
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 remove LegacyProvider (#26433) 2020-10-05 08:33:49 -04:00
unparsed_value.go Avoid leaking sensitive values in undeclared warnings 2019-11-05 17:32:57 -08:00
unparsed_value_test.go backend/local: Handle interactive prompts for variables in UI layer 2019-10-10 10:07:01 -07:00