Slack notifier fails to deploy because it doesn't listen to port 8080 about cloud-build-notifiers HOT 7 CLOSED

Same Issue here, has anyone figured out a fix or work around? I've tried using older images, but haven't

It seems like the requirement for the 8080 came without fixing the code. I don't know Go but it seems like there is no part in the code that asks for port 8080.

My idea is to ask ChatGPT to translate that Go code into Python and fix what's missing. If someone tries this path let know. Too busy at the moment.

from cloud-build-notifiers.

same problem

from cloud-build-notifiers.

@vicpadilla can you help?

from cloud-build-notifiers.

@vicpadilla I'm also having the same issue.

from cloud-build-notifiers.

Same Issue here, has anyone figured out a fix or work around? I've tried using older images, but haven't

from cloud-build-notifiers.

Normally, this error shows up when the provided config yaml is incorrect and the notifier fails to start. You can find more details by going to the Cloud Run page (https://console.cloud.google.com/run) and accessing the container logs.

One possible misconfiguration is that the json template file is not present in GCS. The provided yaml example specifies such file as uri: gs://example-gcs-bucket/slack.json, but there is no specific instruction to upload that JSON file to GCS. You can take the example slack.json file from the link in the documentation and upload it to the correct bucket using the cloud console page, or the gsutil CLI.

If it fails after that fix, please provide some details from the container logs.

from cloud-build-notifiers.