Some questions...

[maccyber]

Some questions...

[cintiadr]

Just to keep you (and whoever lands here from google search) in the loop, I'm using a wrapper script to see if there was a newer version of the tag I'm using on docker-compose file:

https://github.com/openmrs/openmrs-contrib-ansible-docker-compose/blob/master/files/dockerhub-webhook/scripts/deploy-compose-if-newer

It's not the smartest thing I've ever coded, but it does work and allow me to deploy it the way it is right now.
In all fairness, the ability to only trigger a webhook on a certain tag is something that could be done in dockerhub itself.

[maccyber]

Thanks, awesome to see it being used.

Earlier I was out on the same quest as you - to find a good dockerhub-webhook service, but i couldn't find any (good). So decided to write my own.

Added some commits, I changed the lookup of repo names, so in scripts/index.js you now have to define the repo with namespace e.g.

module.exports = {
  'cintiadr/testhook': 'hello.sh something', 
}

1. Got the same error, will look into it.
   Added ability to disable callback to dockerhub see config/index.js
2. Send me a pull request and I'll merge it
3. Added ability to run script with parameters

I will look into tag-support.

[cintiadr]

I did more tests with the callback, and contrary to what the documentation said, it doesn't prevent other webhooks to be triggered. In fact, all webhooks will be triggered at the same time, and they are all showing as success anyway if you look at the webhook history (I suppose that's the 204 we are sending back). I have no idea how or if this callback is supposed to work.
So, while it's a little bit weird, it's not a show stopper.

About the bash: #29
Thanks for the arguments! Even better, I can now even have file redirects:

module.exports = {
  'cintiadr/testhook': 'hello.sh something > /tmp/somefile', 
}

It's brilliant!

[cintiadr]

Based on https://forums.docker.com/t/webhook-pipelines-dont-wait-for-callback/5813/2 and https://forums.docker.com/t/webhook-callback-failed-400-client-error-when-using-autodeploy/10011/6 , I'd assume that it's broken for way more people. I couldn't create any curl command which allowed an update.
Maybe it's now only available for paid repositories?

Anyway, ignoring the callback works just fine for me.

[maccyber]

Ah, thanks for investigating this. I will disable callbacks by default until this is sorted out @ hub-feedback #943.

Cool with the bash-thingy.

[maccyber]

Rewrote the whole thing and added tag support to this maccyber/micro-dockerhub-hook.

Not well tested..