James Bardin

Hi @prahastakumar, Unfortunately the log lines there don't add any more useful information. Your resource's particular state is somehow causing terraform to try and generate an invalid configuration, but without...

Hi @konradzagozda, The result here is what I would expect, because you are validating something which cannot be known at the time of validation. This means it can't be evaluated...

Thanks, that makes it a little more clear what aspect of the behavior you were concerned about. The validation is run when the variable is evaluated, and since the data...

@konradzagozda, variables have dependencies just like anything else that contains references in the configuration, it wouldn't change anything to record them in the state. Resource dependencies are recorded in the...

Turns out this was already fixed in `main` along with some of the other validation refactoring.

Just to add some more context here, The definitions of the provider are not relevant to the panic, the error is related to the evaluation of the `template` variable. Since...

Thanks for the extra info @limakzi, but I'm still not seeing how we get to the `github_repository` evaluation without first visiting `var.template`. I tried making a few different test cases,...

closing to use #36184 as the primary issue which has a more detailed example

Hi @dangyy0626, Thanks for filing the issue. The line numbers in your stack trace don't match up to current versions, are you certain this was pulled from `main`? Your example...

No, a null cty value is perfectly valid, and `r.ProviderMeta` is allowed to be null there. Terraform core sets that to be `null` most of the time, so that is...