Jann Fischer

Yeah, the fix above will address this issue. I'm a little hesitant to put in a patch release (e.g. 0.11.4) tho, because it might break workarounds that people have in...

Hey, apologies for coming so late to this one! I was just thinking, that this is not specific to Helm, because it really is writing the app source YAML, just...

Thanks. I was thinking we had a similar issue reported (and fixed) recently. So either this is a regression, or my memory fails on me. Let me cross check.

Hey @travis-sobeck, the Image Updater - in its default configuration - will change application parameters on the `Application` CRs it updates, effectively changing the `Application`'s spec. I can just guess...

> That being said it would be nice if the these two projects were more compatible .... (unless I'm missing something) I do fully agree with that! We'll see how...

Hey @travis-sobeck, I don't know whether it got lost in formatting, but the contents really should be: ```yaml kustomize: images: - image1 - ... ``` Also, are you using Argo...

> Upgrading to Argo 2.0 has resolved the issue, at least as far as the 'git" write back which in retrospect i do like having the permanent record in the...

Hi, currently it is not possible to use argocd-image-updater with plugins. There is a workaround for Kustomize based plugins, when you are using Git write-back with a kustomization target. But...

The constraint to be used is dependent on the update strategy: * Using `semver` update strategy, the constraint is specifying the allowed versions to update to, as a semantic version...

Unfortunately, I do not have an AWS account to test ECR functionality so I am not able to set up a reproduction scenario here. I have a few questions, tho:...