-
Notifications
You must be signed in to change notification settings - Fork 111
Description
Error: Provider produced inconsistent final plan
When expanding the plan for
module.eks_inner_source.module.addons.kubectl_manifest.secret_manager_external_secrets_store(0] to include new values learned so far during apply, provider
"registry.terraform.io/gavinbunney/kubectl" produced an invalid new value for.uid: was known, but now unknown.
*| Error: Provider produced inconsistent final plan
When expanding the plan for
module.eks_inner_source.module.addons.kubectl_manifest.secret_manager_external_secrets_store(0]
I to include new values learned so far during apply, provider I "registry.terraform.io/gavinbunney/kubectl" produced an invalid new value I for .uid: was known, but now unknown.
| This is a bug in the provider, which should be reported in the provider's I own issue tracker.
Context
• Terraform version: 1.6.6
• Provider version: gavinbunney/kubectiv1.19.0
• Kubernetes: Amazon EKS
• CRDs involved: "secretstores.external-secrets.io', clustersecretstores.external-secrets.io"
• The resources are being applied via kubectlmanifest' using 'yam!_incluster" and metadata.uid" is being tracked.
Workarounds Tried
• Removing the resource from state (terraform state rm')
• Replacing the resource (terraform apply -replace')
• Editing the 'terraform.tfstate' manually
• Verifying CRDs and cluster state via 'kubecti"
• Ensuring the resource does not exist before apply