Open adrianmoisey opened 2 years ago
The more I look into this, the more I wonder if it's something being cached
Even if the response is cached, changing the allowed tool setting should probably bust the cache (or otherwise preclude returning manifests from a disallowed build tool).
Even if the response is cached, changing the allowed tool setting should probably bust the cache (or otherwise preclude returning manifests from a disallowed build tool).
Agreed!
Another method I've been using for testing:
I expect it to fail, but it doesn't fail.
I've dug into the code a but, but I can't figure out how it works.
I'm also not sure how argocd reads the argocd-cm
ConfigMap
Checklist:
argocd version
.Describe the bug
I am attempting to disable kustomize, as described here: https://argo-cd.readthedocs.io/en/stable/user-guide/tool_detection/#disable-built-in-tools Unfortunately kustomize still works
To Reproduce
argocd-cm
kustomize.enable: "false"
to the ConfigMap underdata
Expected behavior
Syncing to fail and guestbook example not deployed
Screenshots
N/A
Version
Logs
I can't find any relevant logs. I also tried to see if I can find useful logs, but could not.