argocd

We would like to use argocd image updater to automatically update the development branch of our application config repo and write back the version to git. This works well. We would then like to promote to test by merging this file into our test branch (which does not use image updater) and eventually prod branch which also does not use image updater. The issue is, each of our applications is na

Describe the bug
When setting up an ArgoCd, and later changing the host the ingress will not be updated with the new host information.

To Reproduce
Do a kubectl apply on something like:

apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: argocd
spec:
  server:
    ingress:
      enabled: true

followed by a kubectl apply on something like:

``

In #139 @christiansiegel wrote:

Some things we might look into before releasing on PyPI:

• support and tests for more than one python version (currently only 3.8 is used in the docker build/test; I think even 3.7 doesn't work at the moment)
• support windows (currently the temporary directory for git checkout is hardcoded to /tmp)
• add proper error message if there is no git ins