Franco Costa

Additional comment: All mentioned fields in the error messages start with ".object" so I guess I could try the workaround below. But, I don't know if it can be dangerous....

``` resource "kubernetes_manifest" "buildbuddy" { manifest = yamldecode(templatefile(var.argocd_application_file, { "app_path" = var.app_path })) } ``` ``` apiVersion: argoproj.io/v1alpha1 kind: Application metadata: name: sdp-apps namespace: argocd annotations: argocd.argoproj.io/sync-options: Delete=false finalizers: -...

Hello @sheneska. Did you have the chance to give a look? Maybe the argocd operator/crds are updating the fields: .object.operation.sync.resources .object.operation.sync.syncOptions .object.operation.sync.revision .object.operation.sync.revision .object.operation.initiatedBy.automated Then, adding "object" to computed fields...

Hello, thanks for you help. I think the urgent question is.. since I saw the updates went through, and also the new state file looks plausible to me (long shot,...

Is it positive there was a regression. Which version should we use then? Can anybody recommend a safe version to use now?