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

Terraform plan removes dynamic variable values from state file #1476

Closed
rcostanzo opened this issue Apr 10, 2015 · 2 comments
Closed

Terraform plan removes dynamic variable values from state file #1476

rcostanzo opened this issue Apr 10, 2015 · 2 comments

Comments

@rcostanzo
Copy link

I'm on 0.4.0 (I tried to test on 0.4.1 but #1466 prevented me). When I run terraform plan, my state file is updated and any dynamic output variable values are lost. This makes terraform output of those values not work afterwards.

Test resource file:

resource "aws_vpc" "extole" {
    cidr_block = "10.1.0.0"
    instance_tenancy = "default"
    enable_dns_support = true
    enable_dns_hostnames = true
}

output "vpc_id" {
    value = "${aws_vpc.extole.id}"
}

Pre-plan tfstate snippet:

{
    "version": 1,
    "serial": 44,
    "modules": [
        {
            "path": [
                "root"
            ],
            "outputs": {
                "vpc_id": "vpc-a50856c0"
            },

Post-plan tfstate snippet:

{
    "version": 1,
    "serial": 45,
    "modules": [
        {
            "path": [
                "root"
            ],
            "outputs": {
            },
@phinze
Copy link
Contributor

phinze commented Apr 10, 2015

Hi there, sorry for the trouble. I think this is a dup of #1369, which is high on our list of bugs to squash. Stay tuned over on that thread for the fix. 👍

@phinze phinze closed this as completed Apr 10, 2015
@ghost
Copy link

ghost commented May 3, 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 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants