You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for opening an issue @MonicaMagoniCom – I suspect the problem may be with your depends_on configuration. Can you try the configuration with your terraform_data resource depending on the kubernetes_namespace directly instead of the var? This would tell us if there's a bug in the provider.
I'm still experiecing the same issue. The namespace is created in the same apply command and it seems that the resource "prepare-pulsar-helm-release" sometimes does not find the namespace even if it was created some steps before.
Maybe do I have to split it into 2 terraform apply?
Terraform version: 1.7.4
Kubernetes provider version: 2.31.0
Kubernetes version: 1.28
I have a module called 'kube' where I create the following namespace:
Then in another module (which has a dependency on the kube module), so it is applied after the 'kube' module, I do:
When doing terraform apply, it correctly creates the namespace, but the local-exec fails with error (even though the ns exists):
The text was updated successfully, but these errors were encountered: