You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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)
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.
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.
The text was updated successfully, but these errors were encountered: