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
Currently we're assuming that the input for the invoke and invoke local command is a string which can be parsed (and will be parsed) into JSON.
invoke
invoke local
However some AWS services assume other inputs.
We should update the invoke and invoke local command to reflect that (see: #2833 (comment) and #2833 (comment)).
Thanks @wxs and @dzimine for bringing this up 👍
The text was updated successfully, but these errors were encountered:
Please take a look at the PR #4036 and see if you're ok with:
--raw
Sorry, something went wrong.
Please take a look at the PR #4036
Great! Thanks for taking a stab at it @dzimine 🎉. The implementation sounds reasonable 👍.
We'll look into it ASAP!
No branches or pull requests
This is a Feature Proposal
Description
Currently we're assuming that the input for the
invoke
andinvoke local
command is a string which can be parsed (and will be parsed) into JSON.However some AWS services assume other inputs.
We should update the
invoke
andinvoke local
command to reflect that (see: #2833 (comment) and #2833 (comment)).Thanks @wxs and @dzimine for bringing this up 👍
The text was updated successfully, but these errors were encountered: