Alex Somesan

I noticed the `kubernetes_manifest` resource you quoted in the description doesn't include `provider` attribute to point to the alias of the kubernetes provider block you also quoted. Can you please...

Hi, unfortunately, I'm not able to reproduce this... it works as expected when I try it. ``` resource "helm_release" "vault" { name = "vault" repository = "https://helm.releases.hashicorp.com" chart = "vault"...

We're having a look at this, but I personally have to familiarise myself with the helm upgrade mechanism itself before I can evaluate this PR. I'm doing that, in the...

@farhan-sayeed is the original version that you are trying to upgrade from also installed through Terraform?

Can you please clarify what versions 1.3.1 and 1.3.0 are referring to? Terraform version? Provider version? Chart version?

Can you confirm if it behaves the same when you set `wait = false` on the `helm_release` resource? https://registry.terraform.io/providers/hashicorp/helm/latest/docs/resources/release#wait

Hi, I'm not 100% sure what kind of answer are you looking for. The module in question IS in fact deemed legacy, as the error message suggests. Are you the...

So the "legacy" designation actually refers to the module containing provider blocks, whereas the preferred "modern" approach is to pre-configure the provider block outside the module and then pass it...

Can you please share the full error message (without "..." redactions)? The one shared here isn't telling much.