Closed reddymh closed 2 years ago
Hmm, never ran into an issue like that. What version of argocd are you running? Can you give further details about how everything is structured on your end?
@travisghansen I have two helm charts which I have published to helm repository and using the below helmfile config I am deploying the helm charts but if there is any change in the templates or delete and re-deploy still it will pick the same old generated/template files. As of now workaround is I have re-create the application with different name so that it will generate updated manifest files.
Below are the details:
Argocd VersionL: 2.2.5
helmfile:
---
repositories:
- name: helm-repo
url: <REPO_URL>/artifactory/helm-repo
oci: false
helmDefaults:
createNamespace: false
timeout: 900
releases:
- name: testapp1
chart: helm-repo/app1
namespace: app1
force: true
createNamespace: true
version: 0.14.0
values:
- ./values/dev/app1-values.yaml
- name: testapp2
chart: helm-repo/app2
namespace: app2
force: true
createNamespace: true
version: 1.13.0
Do you update the chart version in the repo when updating templates?
Do you update chart version in helmfile after updates have been published?
Argocd Helmfile plugin should detect changes when refresh or resync from the repository when we change the templates. Currently its not detecting the change and even if we re-deploy the application the old manifests are cached somewhere.