Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

manifest-generate-paths annotation and Multiple Sources #18267

Open
Emmerson-Miranda opened this issue May 17, 2024 · 0 comments
Open

manifest-generate-paths annotation and Multiple Sources #18267

Emmerson-Miranda opened this issue May 17, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Emmerson-Miranda
Copy link

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"
@Emmerson-Miranda Emmerson-Miranda added the bug Something isn't working label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant