-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
1
-
False
-
-
False
-
-
-
-
GitOps Crimson Sprint 3270
Description of Problem:
While adding the "Subscriptions" in the "NotificationsConfiguration" the changes doesn't get updated in the ConfigMap argocd-notifications-cm and not even in the NotificationsConfiguration CR.
Prerequisites/Environment
OpenShift & GitOps operator
Steps to Reproduce
Edit the default NotificationsConfiguration CR "default-notifications-configuration" in the namespace "openshift-gitops-operator" and try to add the subscription resource as per the official document and save the file.
It is observed that the intended changes regarding the subscription resource doesn't get updated in the ConfigMap argocd-notifications-cm and not even in the NotificationsConfiguration CR.
oc get configmap argocd-notifications-cm NAME DATA AGE argocd-notifications-cm 16 96m $ oc edit notificationsconfigurations default-notifications-configuration apiVersion: argoproj.io/v1alpha1 kind: NotificationsConfiguration metadata: creationTimestamp: "2025-01-01T10:51:06Z" generation: 5 name: default-notifications-configuration namespace: openshift-gitops-operator .... spec: Subscriptions: | subscriptions: | # subscription for on-sync-status-unknown trigger notifications - recipients: - slack:test2 - email:test@gmail.com triggers: - on-sync-status-unknown .... templates: .... $ oc get configmap argocd-notifications-cm NAME DATA AGE argocd-notifications-cm 16 97m
Expected Results
The subscription resource should get created within default NotificationsConfiguration CR and the ConfigMap argocd-notifications-cm should get updated with the respective changes.
Actual Results
It is observed that the intended changes regarding the subscription resource doesn't get updated in the ConfigMap argocd-notifications-cm and not even in the NotificationsConfiguration CR.
Problem Analysis
The yaml configuration block provided in the official document for adding subscription resource in the NotificationsConfiguration CR is having indentation and naming convention issues.
Workaround (If Possible)
Edit the document with correct yaml configuration block for adding the subscription resource in the NotificationsConfiguration CR.
subscriptions: |
- recipients:
- slack:test2
- email:test@gmail.com
triggers:
- on-sync-status-unknown