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

core: Invalid for_each argument messaging improvements #30327

Merged
merged 1 commit into from Jan 10, 2022

Commits on Jan 10, 2022

  1. core: Invalid for_each argument messaging improvements

    Our original messaging here was largely just lifted from the equivalent
    message for unknown values in "count", and it didn't really include any
    specific advice on how to update a configuration to make for_each valid,
    instead focusing only on the workaround of using the -target planning
    option.
    
    It's tough to pack in a fully-actionable suggestion here since unknown
    values in for_each keys tends to be a gnarly architectural problem rather
    than a local quirk -- when data flows between modules it can sometimes be
    unclear whether it'll end up being used in a context which allows unknown
    values.
    
    I did my best to summarize the advice we've been giving in community forum
    though, in the hope that more people will be able to address this for
    themselves without asking for help, until we're one day able to smooth
    this out better with a mechanism such as "partial apply".
    apparentlymart committed Jan 10, 2022
    Copy the full SHA
    56149ed View commit details
    Browse the repository at this point in the history