-
Notifications
You must be signed in to change notification settings - Fork 66
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
Use HTTP GET for list requests #111
base: master
Are you sure you want to change the base?
Conversation
I was not sure how to add default GET parameters to a request model - if there’s a better way let me know. I’ll remove the extra commits later on |
af6add5
to
b5f27da
Compare
Thanks for your PR. I would prefer to add an option that allows the developer to control if he would like to use the |
c2ceb44
to
f7674c9
Compare
Thanks @Haennetz - I've added |
Thanks @orf and nice work there are only some formatting issues. @stormshield-gt is it okay for you if we Marge this PR and you add the tests to #107? |
Thanks! I've fixed the formatting 👍 |
4dc0a53
to
bebeb3f
Compare
I've rebased @stormshield-gt <3 It's a tricky issue: on one hand, switching from LIST to GET is supported by the API and is contractually the same. On the other hand it feels like a breaking change. However perhaps that's over-thinking things: we don't need to be constrained by hyrum's law if we don't want to be, and it's unlikely that this would cause major issues for users given that the Vault API explicitly supports this as an alternative to Perhaps we should just switch things to be |
abe06d2
to
a0b89f8
Compare
Hi, sorry for the late response. I agree we shouldn't constrain ourselves to the hyrum's law. I think it mostly applies when you have a lot of users, and that's not the case currently.
That's the direction I want to go. What do you think @Haennetz? I will be on vacation for a few weeks. |
Sure we can switch completely to GET requests. |
Closes #109
This is the branch we are currently using, I’ll fix it up