terraform/backend/remote/test-fixtures/apply-destroy/apply.log

Terraform v0.11.10

Initializing plugins and modules...
null_resource.hello: Destroying... (ID: 8657651096157629581)
null_resource.hello: Destruction complete after 0s

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.
Change how to fall back from remote to local backend In order to support free organizations, we need a way to load the `remote` backend and then, depending on the used offering/plan, enable or disable remote operations. In other words, we should be able to dynamically fall back to the `local` backend if needed, after first configuring the `remote` backend. To make this works we need to change the way this was done previously when the env var `TF_FORCE_LOCAL_BACKEND` was set. The clear difference of course being that the env var would be available on startup, while the used offering/plan is only known after being able to connect to TFE. 2018-11-15 20:26:46 +01:00			`Terraform v0.11.10`

			`Initializing plugins and modules...`
Implement the remote enhanced backend This is a refactored version of the `remote` backend that was initially added to Terraform v0.11.8 which should now be compatible with v0.12.0. 2018-10-31 16:45:03 +01:00			`null_resource.hello: Destroying... (ID: 8657651096157629581)`
			`null_resource.hello: Destruction complete after 0s`

			`Apply complete! Resources: 0 added, 0 changed, 1 destroyed.`