Edit: Turns out Bitbucket only doesn't send the header when using the Test button. Actual webhook triggers correctly set the header, but still throw a 400 Error but for reasons based on my end.
I tired setting up a webhook for my repository to notify my flux-controller running on my Kubernetescluster, whenever I update my Cluster definition. According to the Documentation, Bitbucket sends the X-Hub-Signature Header when I provide it with a secret, which I did. But this does not seem to be the case and when testing the Connection (Either by using the Button, or by making a Push to my Repository), the Flux-Controller answers with a 400 Error due to the signature missing. Sending a request manually using curl (With the Header set) gets rejected because of a wrong signature (Obviously, since I did not calculate a correct one by Hand), so the missing signature seems to be the Problem. Are there any settings that change Bitbuckets behaviour in this regard, or am I doing something wrong?
