manifest-generate-paths annotation and Multiple Sources

[Emmerson-Miranda]

Hello,

Checklist:

• [ x] I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• [ x] I've included steps to reproduce the bug.
• [ x] I've pasted the output of argocd version.

Context

I have argo applications with two sources:

• The first source is avp-helm plugin. Pull a helm chart and resolve secrets from hashicorp vault (see docs).
• The second source pull helm values from an external git repo (see docs)

The external git repo has a webhook that notifies argo when we push changes.

In my applications I am trying to use 'argocd.argoproj.io/manifest-generate-paths' as described here because I have a mono repo, the value I am using is a relative path inside the external git repo .

argocd.argoproj.io/manifest-generate-paths: ./common-config.yaml;./my-cluster/my-app-override-values.yaml

Describe the bug Looks like 'argocd.argoproj.io/manifest-generate-paths' does not work when I am using multiple sources, because I am getting a warning and application does not get updated.

To Reproduce

• Create some secrets in hashicorp vault.
• Integrate ArgoCD with Hashicorp vault using argocd-vault-plugin-helm as described in your documentation.
• Create a helm chart that use secrets in vault.
• Create an external git repo to store values files for the application.
• Configure your annotation to something similar to argocd.argoproj.io/manifest-generate-paths: ./common-config.yaml;./my-cluster/my-app-override-values.yaml
• Configure webhook in your git repo to notify argo when you push to HEAD
• Push changes to your external git repo

Expected behavior The applications that uses argocd-vault-plugin-helm, external git repos and 'argocd.argoproj.io/manifest-generate-paths' annotation should refresh when a change is happening in one specific file or files inside the external git repo.

Version

I am using argo v2.10.5+335875d

Logs

time="2024-05-16T11:44:36Z" level=warning msg="Failed to store cached manifests of previous revision for app my-app: cache: key is missing"

[blakepettersson]

I think the issue you're having is with argocd-vault-plugin, not with manifest-generate-paths. From taking a quick glance, I cannot see that there's any reason why multi-sources wouldn't work with manifest-generate-paths. IIRC argocd-vault-plugin doesn't support multi-sources at all.