Is argocd.argoproj.io/manifest-generate-paths recursive?
#18999
-
|
Can this annotation have effect when files in subdirectories are changed? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
The list of "affected files" comes either from the SCM webhook payload or from The glob patterns listed in the annotation are evaluated by filepath.Match. So if any pattern matches any affected file, the app will be refreshed. So if you want to match everything in a directory recursively, you can use a value like this: (Note this is based on a quick reading of the code. Probably needs a deep dive and some docs updates/examples.) |
Beta Was this translation helpful? Give feedback.
-
Hm, seems like it may not do a recursive match :( |
Beta Was this translation helpful? Give feedback.
-
|
Does this mean that the manifest paths need to include every subdirectory in order to be part of the refresh paths? For example, if the application path is |
Beta Was this translation helpful? Give feedback.
-
|
Yes. I recommend using rendered manifests into a single file or similar. Also, the new hydrator feature might do something similar. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for clarifying! I found different answers to the same question in the argo-cd Slack channel, which made it a bit confusing. |
Beta Was this translation helpful? Give feedback.
The list of "affected files" comes either from the SCM webhook payload or from
git diff --name-only. In general, these are file paths relative to the repo root.The glob patterns listed in the annotation are evaluated by filepath.Match.
So if any pattern matches any affected file, the app will be refreshed.
So if you want to match everything in a directory recursively, you can use a value like this:
/some-dir/*.(Note this is based on a quick reading of the code. Probably needs a deep dive and some docs updates/examples.)