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
..
init	Initial commit of 'cloud' package	2021-10-28 19:29:09 -05:00
local	insert panic handlers	2021-10-28 11:51:39 -04:00
remote	cloud: Add streamlined 'remote' backend state migration path	2021-11-03 15:07:33 -05:00
remote-state	backend/oss: Removes the ConflictWith tag which on the attributes assume_role* to fix the incompatible error	2021-11-03 11:17:35 +08:00
backend_test.go	Move backend/ to internal/backend/	2021-05-17 14:09:07 -07:00
backend.go	backend/local: Check dependency lock consistency before any operations	2021-10-01 14:43:58 -07:00
cli.go	Move terraform/ to internal/terraform/	2021-05-17 14:09:07 -07:00
operation_type.go	Move backend/ to internal/backend/	2021-05-17 14:09:07 -07:00
operationtype_string.go	Move backend/ to internal/backend/	2021-05-17 14:09:07 -07:00
testing.go	command/workspace_delete: Allow deleting a workspace with empty husks	2021-10-13 13:54:11 -07:00
unparsed_value_test.go	refactor ParseVariableValues into separate operations	2021-10-28 19:29:12 -05:00
unparsed_value.go	refactor ParseVariableValues into separate operations	2021-10-28 19:29:12 -05:00