We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello,
We have a simple hook that accepts the headers and payload as arguments for the script:
{ "id": "microservice", "execute-command": "script.py", "command-working-directory": "/etc/webhook", "include-command-output-in-response": true, "pass-arguments-to-command": [ { "source": "entire-headers" }, { "source": "entire-payload" } ] }
We are trying to send a payload with thousands of keys, but webhook gives this error:
[webhook] 2023/01/19 15:09:55 [94fef6] error occurred: fork/exec /etc/webhook/script.py: argument list too long
Looking around I found this issue/comment which mentioned the stream output approach.
stream output
There is also this PR which implements this stream option.
stream
So I simply wanted to make sure, is the PR and the issue option the same solution? And would it help me to solve my issue?
Any input is appreciated
Best, Dave
The text was updated successfully, but these errors were encountered:
Playing around, i figured out how to use a hook with encoded data:
https://github.com/adnanh/webhook/blob/master/docs/Hook-Examples.md#pass-file-to-command-sample
Added this hook as a workaround.
Sorry, something went wrong.
argument list too long is a linux limitation (if my memory serves me right)
Dont see a solution for this.
No branches or pull requests
Hello,
We have a simple hook that accepts the headers and payload as arguments for the script:
We are trying to send a payload with thousands of keys, but webhook gives this error:
[webhook] 2023/01/19 15:09:55 [94fef6] error occurred: fork/exec /etc/webhook/script.py: argument list too long
Looking around I found this issue/comment which mentioned the
stream output
approach.There is also this PR which implements this
stream
option.So I simply wanted to make sure, is the PR and the issue option the same solution?
And would it help me to solve my issue?
Any input is appreciated
Best,
Dave
The text was updated successfully, but these errors were encountered: