Enhancement in multi source repo and notification

[Shubham1406220]

Hello,

I have setup the multiple source repo setup in applicationset. When notification is triggered the revision section is blank but it is visible when i use a single repo in applicationset. Have i missed any configuration to be setup or it is the limitation of multi source repo setup.

I also want to show the image tag of the application got deployed in notification for the same setup. Is it possible ??

#13177 (comment)

[adrianmiron]

I have the same issue, probably linked to the fact that we have multiple revisions for multiple sources and the app controller doesn't know which one to pick, looking forward to a fix.

[chkp-zivhada]

@Shubham1406220 I don't receive slack notification while application values.yaml file changes ( although Argo applies the change).
This is my ApplicationSet:

apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
  name: main
  namespace: argocd
  finalizers:
    - resources-finalizer.argocd.argoproj.io
spec:
  generators:
  - list:
      elements:
        - appName: grafana
          namespace: monitoring
          repoURL: https://grafana.github.io/helm-charts
          targetRevision: 7.3.0
  template:
    metadata:
      name: "{{appName}}"
      namespace: argocd
      annotations:
        argocd.argoproj.io/manifest-generate-paths: ".;.."
        notifications.argoproj.io/subscribe.on-deployed.slack: argocd-alerts
        notifications.argoproj.io/subscribe.on-sync-failed.slack: argocd-alerts
        notifications.argoproj.io/subscribe.on-sync-succeeded.slack: argocd-alerts
    spec:
      project: default
      sources:
      - repoURL: "{{repoURL}}"
        chart: "{{appName}}"
        targetRevision: "{{targetRevision}}"
        helm:
          valueFiles:
          - "$values/eks/argocd/charts/{{appName}}/values.yaml"
      - repoURL: git@github.com:xxx/devops.git
        targetRevision: eks-new-infra-test
        ref: values
      destination:
        name: in-cluster
        namespace: "{{namespace}}"
      syncPolicy:
        automated:
          prune: true
          selfHeal: true
        syncOptions:
          - CreateNamespace=true

while deploying the application directly using kind:Application, the slack notification sent successfully.
Am I missing something here?

[ebarped]

This issue is somehow related to #19766, because can be fixed by modifying the templates defined in the catalog.

The fix should be close to the changes made in #20237