Manifests drift detection

[olfway]

It seems that kustomization_resource just uses kubectl.kubernetes.io/last-applied-configuration annotation and didn't check real manifests at all

Probably it documented somewhere but it was a big surprise for me

I updated argocd application via argocd web interface and kustomization_resource says there is no difference

But if I check with kustomize build | kubectl diff - I see the difference:

     targetRevision: HEAD
+  syncPolicy:
+    automated:
+      prune: true
+      selfHeal: true

[pst]

Related: #89

[nazarewk]

Is it a sensible approach to change kustomization_resource to kubernetes_manifest and wrapping manifest in yamldecode() to properly detect drift?

[nazarewk]

Nevermind, the kubernetes_manifest seems to want to manage all the fields, including dynamic