James Bardin

Hi @gregmark, Thanks for filing the issue and the minimal reproduction! This appears to be a bug in the upstream [go-cty](https://github.com/zclconf/go-cty) library. We can investigate there how we inadvertently end...

I agree that leaving the bulk of the validation to the provider/sdk is a good idea here. For example, the Min/Max values are not really useful in core, because of...

@mkielar, the issue here happens long before `validate` comes into play. In order to validate the config, the correct providers must be initialized. If the overall provider configuration is not...

The provider block is not simply different syntax for the same thing. The `required_providers` block defined what providers are required by the module and what they will be called, while...

Hi @neiser, Thanks for filing the issue. The actual inputs are not shown here, but I assume that `v.value` is receiving a sensitive value in this case? The reasoning here...

I'm not sure if scattering pieces of the behavior around the docs is the most useful way to document this type of thing, and often makes the documentation harder to...

I don't see any evidence here (yet) of the incorrect provider being assigned within Terraform, but an incomplete configuration could make it act like another provider configuration with the same...

Since we don't have any evidence of an incorrect provider instance being used, I'm going to close this under the assumption that the behavior was an incomplete configuration for a...

Closing since the cycle errors should be resolvable in current releases. The logical problems of using a managed resource in a provider configuration still stand, but that is outside of...

Hello, This crash appears to have been fixed in the time since the issue was filed, so I'm going to close the issue for now. If the same crash can...