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

Backport of NestingSingle blocks can be null into v1.3 #32498

Merged

Conversation

teamterraform
Copy link
Contributor

Backport

This PR is auto-generated from #32463 to be assessed for backporting due to the inclusion of the label 1.3-backport.

The below text is copied from the body of the original PR.


NestingSingle blocks removed from from the config were causing a plan to error out with "... planned for existence but config wants absence". Terraform core was proposing an incorrect value in this case, taking the prior instead as a fallback because a null value was not expected.

Unlike other collection nesting modes, a NestingSingle block not present in the configuration is a null value, and should be allowed when planning a new value rather than building an empty object or falling back to the prior value.

Fixes #32460

@teamterraform teamterraform force-pushed the backport/jbardin/nesting-single-null/socially-engaging-pig branch from 92224a8 to fb69e7f Compare January 11, 2023 16:00
@teamterraform teamterraform force-pushed the backport/jbardin/nesting-single-null/socially-engaging-pig branch from 57eef45 to ed09594 Compare January 11, 2023 16:00
@jbardin jbardin merged commit 8c539ca into v1.3 Jan 11, 2023
@jbardin jbardin deleted the backport/jbardin/nesting-single-null/socially-engaging-pig branch January 11, 2023 16:26
@github-actions
Copy link

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 11, 2023
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.

None yet

2 participants