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

walkDestroy is a form of "apply" #17824

Merged
merged 1 commit into from
Apr 10, 2018
Merged

walkDestroy is a form of "apply" #17824

merged 1 commit into from
Apr 10, 2018

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Apr 10, 2018

When computing the count value, make sure to include walkDestroy with
walkApply, as the former is only a special case of the latter.

When applying a saved plan, the computed count values are lost and we
can no longer query the state for those values. The apply walk was
already considered in the resourceCountMax function, but the destroy
walk was not. This worked when destroying in a single operation
("terraform destroy"), since the state would still be updated with the
latest counts from the plan.

Fixes #17793

When computing the count value, make sure to include walkDestroy with
walkApply, as the former is only a special case of the latter.

When applying a saved plan, the computed count values are lost and we
can no longer query the state for those values. The apply walk was
already considered in the `resourceCountMax` function, but the destroy
walk was not.  This worked when destroying in a single operation
("terraform destroy"), since the state would still be updated with the
latest counts from the plan.
@jbardin jbardin requested a review from mitchellh April 10, 2018 15:48
@mitchellh
Copy link
Contributor

This looks right to me. The never ending tweaks to that exclusion though... ;)

@jbardin jbardin merged commit 5b930df into master Apr 10, 2018
@jbardin jbardin deleted the jbardin/destroy-plan-count branch April 10, 2018 16:06
@ghost
Copy link

ghost commented Apr 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 Apr 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

Successfully merging this pull request may close these issues.

Destroy fails for "cannot parse as integer"
2 participants