terraform/internal/backend/remote
Chris Arcand 779c958fbf cloud: Add streamlined 'remote' backend state migration path
For Terraform Cloud users using the 'remote' backend, the existing
'pattern' prompt should work just fine - but because their workspaces
are already present in TFC, the 'migration' here is really just
realigning their local workspaces with Terraform Cloud. Instead of
forcing users to do the mental gymnastics of what it means to migrate
from 'prefix' - and because their remote workspaces probably already exist and
already conform to Terraform Cloud's naming concerns - streamline the
process for them and calculate the necessary pattern to migrate as-is,
without any user intervention necessary.
2021-11-03 15:07:33 -05:00
..
testdata
backend.go cloud: Add streamlined 'remote' backend state migration path 2021-11-03 15:07:33 -05:00
backend_apply.go backend: Remove Operation.Parallelism field 2021-09-14 10:35:08 -07:00
backend_apply_test.go cloud: TestCloud_backendWithTags 2021-10-28 19:29:10 -05:00
backend_common.go insert panic handlers 2021-10-28 11:51:39 -04:00
backend_context.go core: Functional-style API for terraform.Context 2021-08-30 13:59:14 -07:00
backend_context_test.go core: Functional-style API for terraform.Context 2021-08-30 13:59:14 -07:00
backend_plan.go insert panic handlers 2021-10-28 11:51:39 -04:00
backend_plan_test.go Update go-tfe to 26689e 2021-10-28 19:29:10 -05:00
backend_state.go Move states/ to internal/states/ 2021-05-17 14:09:07 -07:00
backend_state_test.go Update go-tfe to 26689e 2021-10-28 19:29:10 -05:00
backend_test.go backend/remote: Support interop from 0.14 to 1.1 2021-09-24 09:26:09 -04:00
cli.go
colorize.go
remote_test.go
testing.go Update go-tfe to 26689e 2021-10-28 19:29:10 -05:00