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: diffs with only tainted set are non-empty #8167

Merged
merged 1 commit into from
Aug 12, 2016

Conversation

phinze
Copy link
Contributor

@phinze phinze commented Aug 12, 2016

Fixes issue where a resource marked as tainted with no other attribute
diffs would never show up in the plan or apply as needing to be
replaced.

One unrelated test needed updating due to a quirk in the testDiffFn
logic - it adds a "type" field diff if the diff is non-Empty. NBD

Fixes issue where a resource marked as tainted with no other attribute
diffs would never show up in the plan or apply as needing to be
replaced.

One unrelated test needed updating due to a quirk in the testDiffFn
logic - it adds a "type" field diff if the diff is non-Empty. NBD
@phinze phinze force-pushed the b-tainted-no-attrs-still-replaces branch from 9a21dd6 to 3dccfa0 Compare August 12, 2016 22:38
@phinze
Copy link
Contributor Author

phinze commented Aug 12, 2016

Will fix #8032 and #8072

@mitchellh
Copy link
Contributor

LGTM. Looks like we'll be chasing down Empty and Equal bugs for the rest of our days.

@ghost
Copy link

ghost commented Apr 23, 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 Apr 23, 2020
This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants