Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

google_compute_target_pool is not idempotent when using URLs as values from google_compute_instance #46

Closed
hashibot opened this issue Jun 13, 2017 · 1 comment · Fixed by #666
Labels

Comments

@hashibot
Copy link

This issue was originally opened by @jsierles as hashicorp/terraform#9121. It was migrated here as part of the provider split. The original body of the issue is below.


Hi there,

Terraform v0.7.4
google_compute_target_pool

resource "google_compute_target_pool" "loadbalancer" {
  name = "target-pool-loadbalancer-${var.env}"
  instances = ["${google_compute_instance.loadbalancer.*.self_link}"]
  health_checks = ["${google_compute_http_health_check.loadbalancer.name}"]
}

Plan output

~ google_compute_target_pool.loadbalancer
    instances.0: "europe-west1-d/loadbalancer-0-staging" => "https://www.googleapis.com/compute/v1/projects/myproject-com/zones/europe-west1-d/instances/loadbalancer-0-staging"
    instances.1: "europe-west1-d/loadbalancer-1-staging" => "https://www.googleapis.com/compute/v1/projects/myproject-com/zones/europe-west1-d/instances/loadbalancer-1-staging"

Expected Behavior

This value should not be changed on every plan/apply run.

Actual Behavior

On every plan and apply, this resource is modified without makes changes to the configuration.

@hashibot hashibot added the bug label Jun 13, 2017
dghubble added a commit to poseidon/typhoon that referenced this issue Nov 5, 2017
* Instances can be listed by zone/name or self_link URL, but the
provider desires they be in zone/name form, which causes a diff
* hashicorp/terraform-provider-google#46
dghubble-robot pushed a commit to poseidon/terraform-google-kubernetes that referenced this issue Nov 5, 2017
* Instances can be listed by zone/name or self_link URL, but the
provider desires they be in zone/name form, which causes a diff
* hashicorp/terraform-provider-google#46
justaugustus pushed a commit to justaugustus/typhoon-azure that referenced this issue Feb 12, 2018
* Instances can be listed by zone/name or self_link URL, but the
provider desires they be in zone/name form, which causes a diff
* hashicorp/terraform-provider-google#46
@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants