-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack Notifier failed to unmarshal templating JSON #145
Comments
UPDATE: And it works fine. So my guess still, is there is something up with the latest version. |
Seems like this is the commit: b0668da In which case, I'm wondering if one of the variables being passed to the template is has embedded quotes that need to be escaped. I'm looking at my cloud build pub/sub messages and I don't see an obvious problem, however. My best, crazy guess is that it has something to do with some unicode encoded equal sign in the "logUrl" variable. The template looks for "projectId", "id", "status", and "logUrl". The first three are just plain ol' ASCII, no special characters, no quotes, etc. The fourth, logUrl, is |
@dpkirchner I agree that it's the commit you reference, but I don't think it's an issue with the template values. That commit wires the slack notifier up to use a golang template which gets populated over in notifiers.go. I copied the new file
That cleared the errors in the logs, although the notification is not the prettiest. I guess now I can customize it though. Seems like the documentation needs to be updated to reflect that a template for slack attachment blocks needs to be configured. |
Another workaround for folks using the slack notifier with the
|
@dandebiase FYI, using this workaround throws the error below when I run the setup.sh script.
|
For those who face this error unmarsal JSON secretRef: webhook-url
template:
type: golang
uri: gs://xxxx/slack-msg2.json # some comment here |
I have been following these instructions on the GCP documentation page. I have done nothing custom beyond substituting variables.
However, it is not working and I see tons of error messages in the cloud run logs saying:
There is a somewhat similar closed issue here - and the solution was to pin an older version. If thats the case, what version should it be?
Also, how would I set the retry limit invocations to the cloud run service from pubsub? I think would have racked up quite the bill if I had not been looking.
The text was updated successfully, but these errors were encountered: