On Tue, Apr 17, 2018 at 02:47:01PM +0200, Andreas Steinel wrote:
> On Tue, Apr 17, 2018 at 2:09 PM, Fabian Grünbichler
> wrote:
> > there are some places where we really don't know much more than "some
> > object" (because the API call does a bit too much, and can
On Tue, Apr 17, 2018 at 2:09 PM, Fabian Grünbichler
wrote:
> there are some places where we really don't know much more than "some
> object" (because the API call does a bit too much, and can return one
> thing or another depending on the code path taken), but in many
On Tue, Apr 17, 2018 at 02:02:23PM +0200, Andreas Steinel wrote:
> Thank you Fabian for the in depth analysis.
>
> I tried to use the json representation of the API in order to
> automatically extract the schema definitions for a consuming API that
> generates the code based on the found
Thank you Fabian for the in depth analysis.
I tried to use the json representation of the API in order to
automatically extract the schema definitions for a consuming API that
generates the code based on the found definitions of all elements.
This works fine most of the time but failed in this
On Mon, Apr 16, 2018 at 06:03:58PM +0200, Andreas Steinel wrote:
> Hi all,
>
> I tried to access the storage API and looked through [1] to find, that the
>
> GET /nodes/{node}/storage
>
> returns an array of string according to [2] the excerpt is:
>
> "GET" : {
>"description" : "Get status
Hi all,
I tried to access the storage API and looked through [1] to find, that the
GET /nodes/{node}/storage
returns an array of string according to [2] the excerpt is:
"GET" : {
"description" : "Get status for all datastores.",
"method" : "GET",
"name" : "index",
"parameters" : {