Argo-cd: Need a way to "force" refresh an app (invalidate its cache)

Created on 9 Dec 2018  路  4Comments  路  Source: argoproj/argo-cd

With kustomize, it's possible to reference a remote base (e.g. the manifests of a git url tag). The issue with this feature, is that the remote base may change meaning over time, even if the application's source git repository does not change.

We currently cache manifests at the repo server for one day, incorporating the commit SHA as part of the key. This was assumed to be safe to do because the contents of files produced at a git commit sha were considered immutable. But with the potential for a remote kustomize base to change meaning, this assumption is no longer true.

We need to provide an ability to "force" refresh an application, which will get current state of the git repo, as well as the live state (from k8s)

Most helpful comment

Hello @mojtabacazi . Yes this is implemented. You can forcefully refresh cache using argocd app get <appName> --hard-refresh or using by clicking 'Hard Refresh' button in UI:

image

All 4 comments

@alexmt do you know if this is actually implemented ? If so can you point me to the PR or documentation please?

Hello @mojtabacazi . Yes this is implemented. You can forcefully refresh cache using argocd app get <appName> --hard-refresh or using by clicking 'Hard Refresh' button in UI:

image

So that's what that arrow is for, the click hit area is so tiny that I thought it's just a ui bug.
Thank you @alexmt

@alexmt Is it possible to hard-refresh all apps ? either with CLI or the UI

Was this page helpful?
0 / 5 - 0 ratings