You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jbardin opened this issue
Sep 9, 2020
· 1 comment
· Fixed by #26192
Labels
bugconfirmeda Terraform Core team member has reproduced this issuecoreexplaineda Terraform Core team member has described the root cause of this issue in code
When a resource that is planned to be CreateThenDelete because of a forced created_before_destroy from another resource, but the create_before_destroy resource has no changes, the apply process is losing the CreateThenDelete portion of the plan.
Applying this once, and changing resource a's version will cause null_resource.a to produce an invalid plan:
Error: Provider produced inconsistent final plan
When expanding the plan for null_resource.a to include new values learned so
far during apply, provider "registry.terraform.io/hashicorp/null" changed the
planned action from CreateThenDelete to DeleteThenCreate.
This is a bug in the provider, which should be reported in the provider's own
issue tracker.
This is erroneously attributed to the provider, but there is nothing the provider can do to modify the plan action for individual resources
The text was updated successfully, but these errors were encountered:
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
locked as resolved and limited conversation to collaborators
Oct 15, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugconfirmeda Terraform Core team member has reproduced this issuecoreexplaineda Terraform Core team member has described the root cause of this issue in code
When a resource that is planned to be
CreateThenDelete
because of a forcedcreated_before_destroy
from another resource, but thecreate_before_destroy
resource has no changes, the apply process is losing theCreateThenDelete
portion of the plan.For example:
Applying this once, and changing resource a's version will cause
null_resource.a
to produce an invalid plan:This is erroneously attributed to the provider, but there is nothing the provider can do to modify the plan action for individual resources
The text was updated successfully, but these errors were encountered: