You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Take a standard directory based argocd application without the directory param set in the terraform HCL or in the app manifest, add directory and includes
Expected Behavior
The provider should have added to the source block:
directory:
include: '*.yaml'
Actual Behavior
No diff reported
References
By default ArgoCD will infer directory if you just provide a source path in a repo, though we recently hit a bug with configuration mangement plugin resolution that can be avoided if you explicitly put directory, helm, kustomize in the app manifest to avoid the plugin resolution.
I did a simple test by chaning the diff function (see here) and that would fix the issue and properly configure the include key. But still when rerunning Terraform the plan now shows a diff for spec.source.directory.include where I'm not quite sure where this comes from...
Terraform Version, ArgoCD Provider Version and ArgoCD Version
Affected Resource(s)
argocd_application
Terraform Configuration Files
Steps to Reproduce
Take a standard directory based argocd application without the directory param set in the terraform HCL or in the app manifest, add directory and includes
Expected Behavior
The provider should have added to the source block:
Actual Behavior
No diff reported
References
By default ArgoCD will infer directory if you just provide a source path in a repo, though we recently hit a bug with configuration mangement plugin resolution that can be avoided if you explicitly put directory, helm, kustomize in the app manifest to avoid the plugin resolution.
argoproj/argo-cd#15763
Community Note
The text was updated successfully, but these errors were encountered: