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

core: change taint semantics #6894

Merged
merged 3 commits into from May 27, 2016
Merged

core: change taint semantics #6894

merged 3 commits into from May 27, 2016

Conversation

phinze
Copy link
Contributor

@phinze phinze commented May 27, 2016

Rebase of #6600

Sander van Harmelen added 3 commits May 26, 2016 19:55
This means it’s shown correctly in a plan and takes into account any
actions that are dependant on the tainted resource and, vice verse, any
actions that the tainted resource depends on.

So this changes the behaviour from saying this resource is tainted so
just forget about it and make sure it gets deleted in the background,
to saying I want that resource to be recreated (taking into account the
existing resource and it’s place in the graph).
DestroyMode GraphNodeDestroyMode
// If set to true, this resource represents a resource
// that will be destroyed in some way.
Destroy bool
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@svanharmelen This is my favorite part. 😄

Bye DestroyMode! 👋

@phinze
Copy link
Contributor Author

phinze commented May 27, 2016

This is @svanharmelen's code reviewed and rebased by me, just pushed as PR to check the build.

It's green so in we go!

@phinze phinze merged commit 24eaf9a into master May 27, 2016
@phinze phinze deleted the svanharmelen-f-taint-semantics branch May 27, 2016 01:20
@ghost
Copy link

ghost commented Apr 25, 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.

@hashicorp hashicorp locked and limited conversation to collaborators Apr 25, 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

Successfully merging this pull request may close these issues.

None yet

1 participant