argocd-image-updater
argocd-image-updater copied to clipboard
Somehow allow for "Bootstrapping" of writeback values
Is your feature request related to a problem? Please describe.
For our specific workflow, we use a folder structure like /values/generated/{environment}.yaml This is the yaml we write back to when ArgoCD-Image-Updater updates a deployment.
This leads to an issue when creating new applications, that the image updater has not yet touched.
The values that the image updater writes, will not yet have been written, and the application cannot successfully come up, which causes it to be ignored by the image updater, making sure the values never get updated
Describe the solution you'd like An annotation to allow argocd-image-updater to not ignore an application in failed/processing state, allowing for the image updater to write image and tag to a git repo of a 'processing' application
Describe alternatives you've considered We could obviously just prefill the values with some placeholders such as nginx or busybox, however, this seems cluncky and unintuitive
Does force-update annotation work for you?
https://argocd-image-updater.readthedocs.io/en/latest/configuration/images/#forcing-image-updates
Sorry for not answering, i went on vaction. But, no 'force-update' does not work. I get the error
skipping app 'appname' of type 'Directory' because it's not of supported source type
I suspect this is because the application is not valid, as it is based on some values i'd like to write with the image updater