Alex Somesan

Hi, Unfortunately, there isn't much the provider can do about filtering sensitive values. The propagation of the "sensitive" property of a value is handled by Terraform internally and this bit...

@cuttingedge1109 Can you plese share a bit more detail about how those variables used to in provider configuration are set themselves? Also, please include the variable declarations. Is this part...

Could you please share the versions of provider and Terraform that you're using? Also, can you confirm this is happening specifically on Windows?

Were you able to make progress here or is this still affecting you?

Hi, The "status" attribute is removed by the provider logic on purpose. This is becuase the value of status can change on the API side without intervention from Terraform and...

Thanks for reporting this. I can reproduce the issue and it looks like it's indeed a problem in the provider. Note to fixer: it looks like we can't really use...

You can temporarily work around this issue by setting `wait_for_rollout = false` on the affected resource. For example: ``` resource "kubernetes_stateful_set" "test" { metadata { name = "test-1166" } wait_for_rollout...

The exec plugin configuration requires the actual plugin binary to be present. In case of AWS, this is actually the `aws` cli tool. Do you have the `aws` cli tool...

@lwsanty Can you share some details about how the value of `local.configmap_checksum` gets set?

@Ragib95 This is expected behaviour due to a limitation in Terraform that causes it to not recognise the implicit dependency between the Helm resource and the EKS cluster resource. Terraform...