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: destroy graph must connect edges for proper target ordering #10036

Merged
merged 1 commit into from
Nov 11, 2016

Conversation

mitchellh
Copy link
Contributor

This connects the destroy edges so that when a -target is specified on
a destroy, the proper dependencies get destroyed as well.

The command package actually caught this and I added a terraform
context test as well.

This connects the destroy edges so that when a `-target` is specified on
a destroy, the proper dependencies get destroyed as well.
@mitchellh
Copy link
Contributor Author

Merging since tests just failed before this.

@mitchellh mitchellh merged commit 3b86dff into master Nov 11, 2016
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
terraformbot pushed a commit that referenced this pull request Nov 11, 2016
[origin/master] Merge pull request #10036 from hashicorp/b-destroy-order
3b86dff
@stack72 stack72 deleted the b-destroy-order branch December 12, 2016 15:01
@ghost
Copy link

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

1 participant