Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Allow custom webhooks with custom http header + body #12340

Closed
izelnakri opened this issue Jul 27, 2020 · 4 comments
Closed

Feature: Allow custom webhooks with custom http header + body #12340

izelnakri opened this issue Jul 27, 2020 · 4 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@izelnakri
Copy link

Description

Hi there,

I wanted to implement a gitea<->argo CI/CD system, and for this I need to make a HTTP POST request to my argo server with a Bearer token.

In other words in the UI we need a way to add custom http headers and http body(the argo workflow template to trigger via json), not just url and http methods. I think this is an essential feature that gitea needs to support. I can create a simple node.js server that parses the webhooks and makes my requests to the argo server but thats very hacky.

@jolheiser
Copy link
Member

Related or duplicate of #1089?

@izelnakri
Copy link
Author

Yes I had seen/skimmed that issue, the suggestion there seemed more complex and handles more cases. I didn't want to give an impression that I endorse all the suggestions there, although I dont mean I agree or disagree with their approach.

What Im suggesting here is rather adding 2 form sections to Gitea webhooks: http headers and http body(with default prefilled perhaps)

@stale
Copy link

stale bot commented Oct 4, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Oct 4, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Nov 19, 2020
@stale stale bot removed the issue/stale label Nov 19, 2020
@techknowlogick
Copy link
Member

Merging this into #1089 (and the contents of the template can be covered there, incl. headers)

@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

No branches or pull requests

4 participants