Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with lifecycle { ignore_changes = [object] } #2665

Open
feraudet opened this issue Jan 13, 2025 · 1 comment
Open

Crash with lifecycle { ignore_changes = [object] } #2665

feraudet opened this issue Jan 13, 2025 · 1 comment
Assignees
Labels

Comments

@feraudet
Copy link

Terraform Version, Provider Version and Kubernetes Version

on darwin_arm64
+ provider registry.terraform.io/hashicorp/archive v2.2.0
+ provider registry.terraform.io/hashicorp/aws v5.82.2
+ provider registry.terraform.io/hashicorp/helm v2.12.1
+ provider registry.terraform.io/hashicorp/kubernetes v2.16.0

Affected Resource(s)

  • kubernetes_manifest

Terraform Configuration Files

resource "kubernetes_manifest" "secret" {
  manifest = yamldecode(templatefile("${path.module}/external-secret.tftpl", {
    name      = var.name,
    namespace = var.namespace,
    type      = "",
    data = { for s in var.keys : s =>
      {
        secretName = var.type == "new" ? aws_secretsmanager_secret.secret[0].name : data.aws_secretsmanager_secret.secret[0].name,
        property   = s
      }
    }
  }))
  lifecycle {
    ignore_changes = [
      manifest,
      object,
    ]
  }
}

Debug Output

│ Error: Provider produced invalid plan
│
│ Provider "registry.terraform.io/hashicorp/kubernetes" planned an invalid value for .....
....
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Steps to Reproduce

  1. terraform apply

Expected Behavior

object change ignored

Actual Behavior

Crash

References

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@arybolovlev
Copy link
Contributor

Hi @feraudet,

Please share the full error output here.

Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants