Skip to content
This repository has been archived by the owner on Feb 7, 2024. It is now read-only.

Timeout for notification triggers #365

Open
VA-PLE opened this issue Nov 22, 2021 · 0 comments
Open

Timeout for notification triggers #365

VA-PLE opened this issue Nov 22, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@VA-PLE
Copy link

VA-PLE commented Nov 22, 2021

Hello. I use argocd-notifications trigger:

trigger.on-sync-status-unknown: |
  - description: Application status is 'Unknown'
    send:
    - app-sync-status-unknown
    when: app.status.sync.status == 'Unknown'

Which notifies whether the helm chart (from the gitrepo) coincides with what is deployed in kub. Helm repositories and kube cluster are located in different regions and between them from time to time there are network delays. This leads to a false positive notification.

Please either increase the validation time of the inspection or provide tools to manually manage this latency.

@VA-PLE VA-PLE added the enhancement New feature or request label Nov 22, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant