[WIP] Support for generic REST client #57
Conversation
|
@j-griffith As discussed a few weeks back, here's a first attempt at a "dummy" client. It's able to leverage existing Provider and Service clients, so things like authentication and core HTTP calls are automatically handled. Technically low-level calls are already possible in Gophercloud, but there's a good amount of work involved, especially if you're making multiple calls, so I tried to strike a balance between the core calls and the per-package functionality. If you can, at your convenience, let me know what you think or if you see any issues. |
|
Just noticed I can easily add support for URL/query params, too. I'll loop back to this later today. |
|
Awesome! I'll try and look at it ASAP |
This commit adds support for a generic REST actions. These actions allow direct REST communication while still leveraging some of the core Gophercloud client features.
There was a problem hiding this comment.
First pass this look great Joe! I'm going to work on loading it up and trying to implement my own little functional test with some V3.X stuff. I don't want to hold you up because in terms of "looking" at the code it looks great. Just want to make sure things work the way I think they do and make sure I can figure out how to actually write an impl with it. Thanks for hanging in there on this topic and putting this together!
|
@j-griffith All sounds good. I'm not in a rush to merge this, so definitely take your time. I'd rather wait a while to hear feedback from yourself or anyone else who notices this PR open :) |
This commit adds support for a generic REST actions. These actions allow
direct REST communication while still leveraging some of the core
Gophercloud client features.
For #56