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_route doesn't evaluate instance self_link #2485

Closed
seboudry opened this issue Nov 16, 2018 · 4 comments
Closed

google_compute_route doesn't evaluate instance self_link #2485

seboudry opened this issue Nov 16, 2018 · 4 comments
Assignees
Labels
bug forward/review In review; remove label to forward service/compute-vpc

Comments

@seboudry
Copy link

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

> terraform -v
Terraform v0.11.10
+ provider.google v1.18.0

Affected Resource(s)

  • google_compute_route

Terraform Configuration Files

resource "google_compute_route" "route-self-link" {
  name              = "route-self-link"
  network           = "${google_compute_network.cluster.name}"
  tags              = ["k8s"]

  dest_range        = "0.0.0.0/0"

  next_hop_instance = "${google_compute_instance.nat.self_link}"
  priority          = 700
}

Expected Behavior

Field next_hop_instance with ${google_compute_instance.nat.self_link} as plain text evaluated to corresponding instance value.

Actual Behavior

  + google_compute_route.route-self-link
      id:                                                  <computed>
      dest_range:                                          "0.0.0.0/0"
      name:                                                "route-self-link"
      network:                                             "cluster-net"
      next_hop_instance:                                   "${google_compute_instance.nat.self_link}"
      next_hop_network:                                    <computed>
      priority:                                            "700"
      project:                                             <computed>
      self_link:                                           <computed>
      tags.#:                                              "1"
      tags.1699766702:                                     "k8s"

Steps to Reproduce

  1. terraform plan

References

I first tough that my problem was linked to the following issue but it was closed

@ghost ghost added the bug label Nov 16, 2018
@seboudry seboudry changed the title google_compute_route does't evaluate instance self_link google_compute_route doesn't evaluate instance self_link Nov 16, 2018
@rileykarson
Copy link
Collaborator

Are you getting an error when you run terraform apply? At plan time, Terraform doesn't have enough information to know what the self link is, and it will only be able to interpolate it at apply time.

@rileykarson
Copy link
Collaborator

I'm going to close this out because I think it's expected behaviour, but feel free to reopen if you're encountering an error here.

@seboudry
Copy link
Author

seboudry commented Jan 9, 2019

Hi! Sorry for late response.
Issue solved now (tested with Google provider v1.20.0) even if VM instance not created yet.

Before, I have used a workaround by specifying both instance name (instead of self link) and instance zone:

resource "google_compute_route" "route-self-link" {
  name                   = "route-self-link"
  network                = "${google_compute_network.cluster.name}"
  tags                   = ["k8s"]

  dest_range             = "0.0.0.0/0"

  next_hop_instance      = "${google_compute_instance.nat.name}"
  next_hop_instance_zone = "${google_compute_instance.nat.zone}"
  priority               = 700
}

@ghost ghost removed the waiting-response label Jan 9, 2019
@ghost
Copy link

ghost commented Jan 17, 2019

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 Jan 17, 2019
@github-actions github-actions bot added forward/review In review; remove label to forward service/compute-vpc labels Jan 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug forward/review In review; remove label to forward service/compute-vpc
Projects
None yet
Development

No branches or pull requests

2 participants