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

Cannot write computed values to nested attributes #929

Closed
sparkprime opened this issue Feb 5, 2015 · 6 comments · Fixed by #1095
Closed

Cannot write computed values to nested attributes #929

sparkprime opened this issue Feb 5, 2015 · 6 comments · Fixed by #1095

Comments

@sparkprime
Copy link
Contributor

On master, the following yields an empty string in that output variable, and empty strings are visible when doing terraform show. However I have annotated the source code and seen that d.Set(...) is being called correctly in resourceComputeInstanceRead

That makes me wonder if there is a bug in core? Or maybe the code in resourceComputeInstanceRead is wrong (in which case what should it look like?)

resource "google_compute_instance" "test0" {
    name = "test0"
    machine_type = "g1-small"
    zone = "us-central1-a"

    disk {
        image = "debian-7-wheezy-v20140814"
    }

    network {
        source = "default"
    }
}
output "network_ip" {
    value = "${google_compute_instance.test0.network.0.internal_address}"
}
@mitchellh
Copy link
Contributor

Can you get me the TF_LOG=1 output for the bare (no state) apply?

@mitchellh mitchellh self-assigned this Feb 17, 2015
@mitchellh mitchellh added the waiting-response An issue/pull request is waiting for a response from the community label Feb 17, 2015
@mitchellh mitchellh removed their assignment Feb 17, 2015
@sparkprime
Copy link
Contributor Author

@mitchellh
Copy link
Contributor

Oh, and now the terraform show output (with state)

@sparkprime
Copy link
Contributor Author

@phinze phinze removed the waiting-response An issue/pull request is waiting for a response from the community label Feb 21, 2015
@mitchellh
Copy link
Contributor

Ah, I figured this out. This is just totally broken on master.

@ghost
Copy link

ghost commented May 4, 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 have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators May 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants