You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
Every permutation or attempt to reformat this call to get the Kustomize details for an app (app-deployed) fails every time. As written above this call fails with the following:
failed to notify 'console:stdout': template: app-deployed:23:17: executing "app-deployed" at <call .repo.GetAppDetails>: error calling call: runtime error: invalid memory address or nil poi
nter dereference
Diagnostics
We are running Azure Redhat Openshift on the latest version (4.8)
What version of Argo CD and Argo CD Notifications are you running?
ArgoCD: v2.1.6
ArgoCD Notifications: v1.2.0
I am assuming this is me not understanding the proper call .repo.GetAppDetails syntax and the current documentation is a one-liner; this could probably be improved to show an example of how to properly configure this block in a template file.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
Following the documentation in notifications, trying to get the
KustomizeAppSpec
like so:Every permutation or attempt to reformat this call to get the Kustomize details for an app (
app-deployed
) fails every time. As written above this call fails with the following:Diagnostics
We are running Azure Redhat Openshift on the latest version (4.8)
What version of Argo CD and Argo CD Notifications are you running?
ArgoCD:
v2.1.6
ArgoCD Notifications:
v1.2.0
I am assuming this is me not understanding the proper
call .repo.GetAppDetails
syntax and the current documentation is a one-liner; this could probably be improved to show an example of how to properly configure this block in a template file.Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.
The text was updated successfully, but these errors were encountered: