James Bardin

I'm not sure what the overall intent of the change was supposed to be, but this immediately breaks implied provider configuration coming from root modules since it is now relying...

IIUC I think we have 2 disparate requirements here, both of which are satisfied with possible current configuration, however it would definitely be more user-friendly if these were not up...

Closing since the premise that destroy ordering wasn't already well-defined doesn't hold true.

Hi @sblask, What you have described here is the intended design of the type system within the Terraform language. Implicit type conversion is always done on assignment within the language,...

Hi @wyardley, For a quick reason as to why this fails, the value `google_secret_manager_secret.this.labels` is defined as a `map(string)` while the literal value in the config is a `object({foo=string,baz=string})`, so...

This issue is fine to track whatever improvements we may be able to come up with. I wouldn't limit conversions to only object/map if we're going to implement something that...

The fact that nested structural attributes can't be declared from the CLI was a known limitation and tradeoff when the S3 backend added them to their schema, and they could...

Taking a look at this provider's schema, the block does contain some attributes marked sensitive. I think the prior version of the renderer would only hide individual sensitive attributes, while...

@apparentlymart, just to make sure I was clear in my summary above, the old behavior _was_ hiding the entire block if it were dynamically marked sensitive (there are tests for...

Oh, thank you! I missed that you confirmed that the backend is a set data structure, and was thinking of it as a list specifically because it was _not_ being...