Open alex1989hu opened 3 years ago
Hi @alex1989hu, wonder if https://github.com/argoproj-labs/argocd-notifications/pull/132 fixes this issue you reported.
Hello @mayzhang2000, I am afraid it did not.
Image used: docker.io/argoprojlabs/argocd-notifications@sha256:cfaf4d1c6da8ddd06d82707af2c02beae0b987606bb8eceda00dbb30b4957c59
I see the same logs and behaviour what I reported.
Hi @alex1989hu The latest version is v1.1.1 now, then maybe this issue is fixed on latest version. If you have already used it, would you share reproduce or not, please?
I commented on the PR https://github.com/argoproj-labs/argocd-notifications/pull/129#issuecomment-732787069:
Unfortunately, #129 did not fix it. Also, the new annotation from #129 is not set.
So jumping back to state before #116 or
v0.7.0
makes argocd-notifications work.Version: I have deployed the recently version if the image after/before https://github.com/argoproj-labs/argocd-notifications/pull/129
Logs:
Configuration:
ConfigMap: