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

0.13 backport 26343 #26344

Merged
merged 2 commits into from
Sep 24, 2020
Merged

0.13 backport 26343 #26344

merged 2 commits into from
Sep 24, 2020

Conversation

jbardin
Copy link
Member

@jbardin jbardin commented Sep 22, 2020

This is a 0.13 backport of #26343

Update the create_before_destroy status in state during refresh, in order to reflect the current configuration.

It's not quite as complete as the 0.14 version, as we can't update the forced create_before_destroy behavior due to the refresh walk not having that information, but it still allows a misconfigured resource to be manually updated in state with a refresh.

In order to save any changes to lifecycle options, we need to record
those changes during refresh, otherwise they would only be updated when
there is a change in the resource to be applied.
@jbardin jbardin requested a review from a team September 22, 2020 21:13
@codecov
Copy link

codecov bot commented Sep 22, 2020

Codecov Report

Merging #26344 into v0.13 will increase coverage by 0.00%.
The diff coverage is 84.61%.

Impacted Files Coverage Δ
terraform/eval_state.go 58.01% <75.00%> (+0.66%) ⬆️
terraform/node_resource_refresh.go 89.08% <100.00%> (+0.32%) ⬆️
terraform/node_resource_plan.go 92.23% <0.00%> (-1.95%) ⬇️
dag/marshal.go 53.42% <0.00%> (-1.37%) ⬇️

@jbardin jbardin merged commit 89c8e8c into v0.13 Sep 24, 2020
@jbardin jbardin deleted the jbardin/backport-26343 branch September 24, 2020 14:04
@ghost
Copy link

ghost commented Oct 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.

@ghost ghost locked as resolved and limited conversation to collaborators Oct 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.

2 participants