github.com/argoproj/argo-cd/v2@v2.10.9/docs/operator-manual/notifications/troubleshooting.md (about)

     1  `argocd admin notifications` is a CLI command group that helps to configure the controller
     2  settings and troubleshoot issues. Full command details are available in the [command reference](../../user-guide/commands/argocd_admin_notifications.md).
     3  
     4  ## Global flags
     5  The following global flags are available for all sub-commands:
     6  
     7  * `--config-map` - path to the file containing `argocd-notifications-cm` ConfigMap. If not specified
     8  then the command loads `argocd-notification-cm` ConfigMap using the local Kubernetes config file.
     9  * `--secret` - path to the file containing `argocd-notifications-secret` ConfigMap. If not
    10  specified then the command loads `argocd-notification-secret` Secret using the local Kubernetes config file.
    11  Additionally, you can specify `:empty` to use empty secret with no notification service settings. 
    12  
    13  **Examples:**
    14  
    15  * Get a list of triggers configured in the local config map:
    16  
    17      ```bash
    18      argocd admin notifications trigger get \
    19        --config-map ./argocd admin notifications-cm.yaml --secret :empty
    20      ```
    21  
    22  * Trigger notification using in-cluster config map and secret:
    23  
    24      ```bash
    25      argocd admin notifications template notify \
    26        app-sync-succeeded guestbook --recipient slack:argocd admin notifications
    27      ```
    28  
    29  ## Kustomize
    30  
    31  If you are managing `argocd-notifications` config using Kustomize you can pipe whole `kustomize build` output
    32  into stdin using `--config-map -` flag:
    33  
    34  ```bash
    35  kustomize build ./argocd-notifications | \
    36    argocd-notifications \
    37    template notify app-sync-succeeded guestbook --recipient grafana:argocd \
    38    --config-map -
    39  ```
    40  
    41  ## How to get it
    42  
    43  ### On your laptop
    44  
    45  You can download the `argocd` CLI from the GitHub [release](https://github.com/argoproj/argo-cd/releases)
    46  attachments.
    47  
    48  The binary is available in the `quay.io/argoproj/argocd` image. Use the `docker run` and volume mount
    49  to execute binary on any platform. 
    50  
    51  **Example:**
    52  
    53  ```bash
    54  docker run --rm -it -w /src -v $(pwd):/src \
    55    quay.io/argoproj/argocd:<version> \
    56    /app/argocd admin notifications trigger get \
    57    --config-map ./argocd-notifications-cm.yaml --secret :empty
    58  ```
    59  
    60  ### In your cluster
    61  
    62  SSH into the running `argocd-notifications-controller` pod and use `kubectl exec` command to validate in-cluster
    63  configuration.
    64  
    65  **Example**
    66  ```bash
    67  kubectl exec -it argocd-notifications-controller-<pod-hash> \
    68    /app/argocd admin notifications trigger get
    69  ```
    70  
    71  ## Commands
    72  
    73  The following commands may help debug issues with notifications:
    74  
    75  * [`argocd admin notifications template get`](../../user-guide/commands/argocd_admin_notifications_template_get.md)
    76  * [`argocd admin notifications template notify`](../../user-guide/commands/argocd_admin_notifications_template_notify.md)
    77  * [`argocd admin notifications trigger get`](../../user-guide/commands/argocd_admin_notifications_trigger_get.md)
    78  * [`argocd admin notifications trigger run`](../../user-guide/commands/argocd_admin_notifications_trigger_run.md)
    79  
    80  ## Errors
    81  
    82  {!docs/operator-manual/notifications/troubleshooting-errors.md!}