every-plan-output.txt

cgravier@cgravier-vm ~/test
$ terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

google_compute_instance_template.test: Refreshing state... (ID: test)
google_compute_health_check.test: Refreshing state... (ID: test)

google_compute_region_instance_group_manager.test: Refreshing state... (ID: test)
google_compute_region_backend_service.test: Refreshing state... (ID: test)

------------------------------------------------------------------------

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  ~ google_compute_region_backend_service.test
      backend.27530698.description:   "" => ""
      backend.27530698.group:         "https://www.googleapis.com/compute/v1/projects/************/regions/us-east1/instanceGroups/test" => ""
      backend.3555381573.description: "" => ""
      backend.3555381573.group:       "" => "https://www.googleapis.com/compute/beta/projects/************/regions/us-east1/instanceGroups/test"


Plan: 0 to add, 1 to change, 0 to destroy.

------------------------------------------------------------------------

Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.