Creating custom helm values file when it doesn't exist

[asmeirs]

Is your feature request related to a problem? Please describe.
I am using helm with git write-back method, and to avoid the conflicts I am creating an additional values-image.yaml values file in a directory that I need for image-updater to write into. Default values.yaml file that is automatically created in the root of the repository when write-back tagret is not specified beyond "helmvalues" doesn't suit me because I have multiple helm releases utilising argocd image updater in the same repository.

I would like to have a possibility to automate this process and add autocreation of the file in a custom directory with a custom filename. Now if I specify a non-existent file in the config, the application is skipped with a following log:

level=warning msg="skipping app 'argocd/app-name' of type 'Directory' because it's not of supported source type" application=app-name namespace=argocd

Describe the solution you'd like
Probably some additional setting like this would help:

spec:
  writeBackConfig:
    method: "git"
    gitConfig:
      writeBackTarget: "helmvalues:/path/to/custom-values.yaml"
   -> createValuesFileIfNotExists: true

[dkarpele]

Thanks for reporting.
Do you have the same issue with the annotation-based Image Updater version 0.17?

[asmeirs]

Thanks for reporting. Do you have the same issue with the annotation-based Image Updater version 0.17?

Yes, that happened exactly in 0.17.0. I haven't tried it yet on version 1.0.0 because AFAIK it had (maybe still has?) other problems with the helm & git write-back method, like freshly closed #1335

[dkarpele]

Are you sure?
The config in your initial messages is related only to the CRD based version 1.0.1.
For 0.17 consider using annotations that start with argocd-image-updater.argoproj.io

By the way the config at the bottom of the Git Write-Back Target section looks like yours.

[asmeirs]

Sorry for the confusion, probably should've specified that - I am using the annotations configurations right now, that's right, but I would love to migrate to v1.0.0+ in the nearest future and I just guessed it wouldn't make sense to request this feature for the 0.x versions, so referenced a possible config extension for the ImageUpdater CR instead

[asmeirs]

For the reference, my current annotations setup is really similar to the one in this official example: https://github.com/chengfang/image-updater-examples/blob/main/write-helmvalues/app/write-helmvalues.yaml

[dkarpele]

Thanks for clarifying. It means this is not a regression in 1.0.1.
We will look into it.