Backport of docs: create_before_destroy meta-attribute propagation into v1.5 #33580
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #32279 to be assessed for backporting due to the inclusion of the label 1.5-backport.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
I've spent quite a lot of time to figure out the fact
create_before_destroy
meta-attribute propagates to all dependencies. Seems like I was not the only one who found this non-intuitive (GitHub issue). I think it's worth noting this behaviour in the documentation explicitly. I don't mind changing the text by maintainers if there is a better English variant.Explains: hashicorp/terraform-provider-kubernetes#1906
CHANGELOG
create_before_destroy
meta-attribute propagation behaviour