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

--additional-params argument not working? #29

Open
shaunhurley opened this issue Apr 3, 2022 · 1 comment
Open

--additional-params argument not working? #29

shaunhurley opened this issue Apr 3, 2022 · 1 comment

Comments

@shaunhurley
Copy link

It appears that parameters passed into a GET method call with the --additional-params options are being ignored.

I'm able to successfully invoke DELETE, POST, PUT - so my cognito elements and the basic mechanisms are all good - and I can call GET with a path parameter, however anything I try to pass in as a querystring is ignored.

I've tried with escaped double quote JSON from windows i.e. --additional-params "{\"name\":\"value\"}" as well as standard singe quoted JSON under Linux i.e. --additional-params '{"name":"value"}'

Note: the escaped quotes succeeds for JSON submitted in the --body parameter under window.

Am I missing something obvious?

Thanks!

@shaunhurley
Copy link
Author

shaunhurley commented Apr 3, 2022

OK, so when I RTFM really really closely, I figured it out i.e. that the query string params have to be wrapped in a {"queryParams": {}"} inside the additional-params arguments in order to be picked up.

I feel like it wouldn't hurt to call that it out in the spec for the additional-params parameter further up in the readme, rather than embedded in the example further down?

Pull Request would be accepted? :)

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

No branches or pull requests

1 participant