This repository has been archived by the owner on Jan 29, 2022. It is now read-only.
NoMethodError at /payload with Bitbucket Server 7.4 webhook #134
Labels
Comments
|
Could be that Bitbucket changed their webhook json yet again. I know @alexjfisher and I have updated the bitbucket webhook parser multiple times since the start of the project for that very reason. I'll look at it later tonight |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
With an install of puppet-webhook 2.1.1 on CentOS 7, I am getting the following error when Bitbucket Server 7.4 (upgraded just to check, this was also failing on 6.10):
I have made the change I referenced in #131, changing the environment to production. If I take the payload that Bitbucket says it sent and send that using curl, it does seem to arrive at at the webhook endpoint.
curl -X POST -H "Content-Type: application/json" -H "X-Request-Id: 27973332-ddc5-466c-a9d4-6d277603f28e" -H "X-Event-Key: repo:refs_changed" -d '{"eventKey":"repo:refs_changed","date":"2020-07-16T20:10:50+0000","actor":{"name":"asdf","emailAddress":"[email protected]","id":52,"displayName":"Asdf","active":true,"slug":"asdf","type":"NORMAL","links":{"self":[{"href":"https://<redacted user link>"}]}},"repository":{"slug":"puppet-control-repo","id":36,"name":"Puppet Control Repo","hierarchyId":"1d2810d27d614aecda49","scmId":"git","state":"AVAILABLE","statusMessage":"Available","forkable":true,"project":{"key":"SOMEKEY","id":1,"name":"Some Name","public":false,"type":"NORMAL","links":{"self":[{"href":"<Link redacted>"}]}},"public":false,"links":{"clone":[{"href":"ssh://git@<Link redacted>/puppet-control-repo.git","name":"ssh"},{"href":"https://<link redacted>/puppet-control-repo.git","name":"http"}],"self":[{"href":"https://<link redacted>/repos/puppet-control-repo/browse"}]}},"changes":[{"ref":{"id":"refs/heads/random_crap","displayId":"random_crap","type":"BRANCH"},"refId":"refs/heads/random_crap","fromHash":"74f3085d0e509107ade95595f094d9598aa0a69f","toHash":"4387a00d00faed6572f6d07422ed852e5004c3ec","type":"UPDATE"}]}' 'http://localhost:9292/payload' -k -qseems to work just fine, though, when run from the host that the server is running on.Trying to understand what my next debugging step should be - as best I can tell, the data object isn't getting initialized somewhere, but I'm not sure what's different in how BB is sending the webhook.
The text was updated successfully, but these errors were encountered: