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.

Sign up for GitHub

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

Jump to bottom

don't panic with a null list block value in config #32428

Merged
merged 1 commit into from Jan 4, 2023
Merged

don't panic with a null list block value in config #32428

merged 1 commit into from Jan 4, 2023

Commits on Dec 21, 2022

  1. don't panic with a null list block value in config 

    Using ignore_changes with a list block, where the provider returned an
invalid null value for that block, can result in a panic when validating
the plan.

Future releases may prevent providers from storing a null block in
state, however we can avoid the panic for now. Only the NestingList case
needs to be handled, because legacy providers only have list and set
blocks, and the set case does not use the config value.
    @jbardin
    jbardin committed Dec 21, 2022
    Copy the full SHA
    ea193d5 View commit details
    Browse the repository at this point in the history