Open aku opened 3 years ago
This is not an actual webhook registry_package
event.
It just checks what the webhook sends to keel, but Keel didn't implement it. So, you can safely ignore this error.
However Github registry_package event is working fine.
@DingGGu could you clarify?
I've exposed Keel's endpoint (/v1/webhooks/github) on my site (lets say https://mysite.com/webhook) Then I've configured GitHub to call this web hook when package is updated
However, it does not work 'cause Keel receives data mentioned above and can't handle it
What am I missing here? Can I use keel with GitHub Container Registry?
Currently, Keel does not support Github Container Registry. ghcr.io/.../...
It only works with Github Package (Legacy version of Github Container Registry) that image name starts with docker.pkg.github.com/.../.../...
I submitted pull request(https://github.com/keel-hq/keel/pull/583) for ghcr yesterday.
@DingGGu cool! looking forward to test it
This appears to have been merged. Why is this still open? ghcr.io does not appear to be working for me...is that the reason?
Yes, it's also not working for me
There is a commented out version of the call to addJob in watcher.go (line 192) which includes the credentials.
// err = w.addJob(imageRef, registryUsername, registryPassword, schedule)
err = w.addJob(image, image.PollSchedule)
It appears that addJob now includes a call to GetCredentials but I don't know what it's expecting for this use case...can anyone provide details on what secret and/or environment variables are expected for ghcr.io? Guessing I missed it in the docs?
Hey, I would be also interested in an answer.
It seems that GitHub Packages web hook is outdated. The code here https://github.com/keel-hq/keel/blob/master/pkg/http/github_webhook_trigger.go does not match the payload sent by GitHub which results in errors
Example of payload: