terraform-provider-kubernetes
terraform-provider-kubernetes copied to clipboard
terraform plan for crd called `external secrets` , with `lifecycle { ignore_changes = all }` , got exception.
Terraform Version, Provider Version and Kubernetes Version
host: wsl2
Terraform v1.0.10
on linux_amd64
+ provider registry.terraform.io/hashicorp/helm v2.4.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.6.1
+ provider registry.terraform.io/hashicorp/random v3.1.0
+ provider registry.terraform.io/hashicorp/vault v3.0.0
+ provider registry.terraform.io/integrations/github v4.18.0
+ provider registry.terraform.io/oboukili/argocd v2.1.0
Your version of Terraform is out of date! The latest version
is 1.0.11. You can update by downloading from https://www.terraform.io/downloads.html
Affected Resource(s)
- kubernetes crd -- external-secrets
Terraform Configuration Files
resource "kubernetes_manifest" "external_secrets_environment" {
manifest = {
apiVersion = "external-secrets.io/v1alpha1"
kind = "ExternalSecret"
metadata = {
name = "${var.kubernetes_secret_name}"
namespace = var.create_kubernetes_namespace ? "${kubernetes_namespace.external_secret_namespace[0].metadata.0.n\
ame}" : "${var.namespace}"
}
spec = {
secretStoreRef = {
name = "${kubernetes_manifest.external_secrets_store.manifest.metadata.name}"
kind: "SecretStore"
}
refreshInterval = "1h"
target = {
name = "${var.kubernetes_secret_name}"
creationPolicy = "Owner"
}
dataFrom = [
{
key = "kv/environment"
},
]
}
}
lifecycle {
ignore_changes = all
}
}
Debug Output
Panic Output
Steps to Reproduce
terraform plan
Expected Behavior
should be able to update
Actual Behavior
panic.
Important Factoids
Nah
References
Nah
Community Note
Nah
Hi @NagleZhang,
There were a few improvements in the kubernetes_manifest resource since you reported this issue. Could you please try the latest provider version and let us know if the issue still presents?
Thank you!
Marking this issue as stale due to inactivity. If this issue receives no comments in the next 30 days it will automatically be closed. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. This helps our maintainers find and focus on the active issues. Maintainers may also remove the stale label at their discretion. Thank you!