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

Option to pass stdin to the executing command #190

Open
adnanh opened this issue Nov 6, 2017 · 2 comments
Open

Option to pass stdin to the executing command #190

adnanh opened this issue Nov 6, 2017 · 2 comments

Comments

@adnanh
Copy link
Owner

adnanh commented Nov 6, 2017

Since command arguments and environment variable content have limits on the size, we could implement option to pass request values via stdin.

Definition could look something like:

"pass-stdin-to-command": [
  { "source": "payload", "name": "something" },
  { "source": "string", "name": "blah blah" }
]

Questions

What format should we use to encode these values so scripts can easily figure out which content resembles which value

  1. We could use newline as value separator, but then we'd have to escape all newlines in the actual value.

  2. Other option would be something like HTTP is doing when sending multipart messages by using boundaries.

  3. Third option would be to encode data using JSON? Tools like jq make this an easy task to handle in shell scripts.

@dcj
Copy link

dcj commented Nov 15, 2017

My 2 cents would be to restrict this feature only the entire-payload.
Smaller things could be passed in as args or env vars.

If not, then I would vote for your option 3, encode it as JSON

@danihodovic
Copy link

My 2 cents would be to restrict this feature only the entire-payload.

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants