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

Outputs which no longer exist in the configuration linger forever #1714

Closed
bitglue opened this issue Apr 28, 2015 · 2 comments · Fixed by #1734
Closed

Outputs which no longer exist in the configuration linger forever #1714

bitglue opened this issue Apr 28, 2015 · 2 comments · Fixed by #1734
Assignees

Comments

@bitglue
Copy link

bitglue commented Apr 28, 2015

If I had to guess, as a consequence of #1369.

Start with a simple configuration:

output "foo" {
    value = "bar"
}

Run terraform apply and you will see:

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

  foo = bar

Now truncate the configuration to be an empty file. terraform apply again. The output, despite no longer existing in the configuration, still exists in the output:

Apply complete! Resources: 0 added, 0 changed, 0 destroyed.

Outputs:

  foo = bar

I'd expect no outputs, since none are declared in the configuration.

@radeksimko
Copy link
Member

👍 I've encountered this too.

@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.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants