[Iplant-api-dev] Agave API changes

[Rion Dooley]

Thanks for the feedback, Cornel. I’m hoping the community can help us improve the migration guide with their own experiences. We are filling in things we run across as we update our client tooling, but we are obviously going to miss things. We really count on champions like you, who want the process to be easier, and who want to give back to the community, to help us identify our blindspots and improve the documentation. If it would be easier, I’m happy to start up a google doc where anyone can add things they find as they come across them and I will just consolidate, format, and expand the information in the Google doc into the migration guide.

I verified your calls to the Files service and you’re right. The bug is in the mediator sitting in front of the actual API services. That’s where the json/xml and formatting discrepancy is coming from and that’s also what’s dropping all PUT requests. I apologize for the problem. I’m bringing this to Joe’s attention. he’s the one in charge of our identity and auth server where this piece lives. He’ll get this squared away asap. We’ll try to update the formatting asap as well. Thanks again for bringing this to our attention and as always, thanks for helping us make a better product for everyone.

--
Rion




On Dec 11, 2013, at 9:46 PM, Cornel Ghiban <ungreen at gmail.com<mailto:ungreen at gmail.com>> wrote:

Thanks, Rion.

Perhaps the migration guide will get updated too :)

Now, I was trying to create a directory. (all the PUT operations bellow used to work on the dev server, but don't not on the live one).

PUT https://agave.iplantc.org/files/2.0/media/ghiban with this content:
'action=mkdir&path=Agave_API_test_313.02926325904&'

The live docs say it's the right way.

But I get an error:

<am:fault xmlns:am="http://wso2.org/apimanager"<http://wso2.org/apimanager>><am:code>403</am:code><am:type>Status report</am:type><am:message>Runtime Error</am:message><am:description>No matching resource found in the API for the given request</am:description></am:fault>

When trying to rename a file/directory I get this error:

{"status":"error","message":"File operation failed could not execute native bulk manipulation query","version":"2.0.0-SNAPSHOT-rf64a967"}


Also, could we get the responses from the server, successful or not, in the same format?
For example the auth requests is a simple json:

{"token_type":"bearer","expires_in":1033,"refresh_token":"....","access_token":"...."}

 while listing the files gives us
{"status":"success","message":null,"version":"2.0.0-SNAPSHOT-rf64a967","result":[{...}]

When the Auth fails because of a bad secret:key combination  we get something like this:
{"error":"invalid_client","error_description":"Client Authentication was failed."}

It would be nice to know we're going to get a JSON object or something else, but always the same format.

Thanks,
Cornel


On 12/11/2013 09:45 PM, Rion Dooley wrote:
Yes. What you see in the live docs, tutorials, quickstarts, and cli is correct and current.

-
Rion

----- Reply message -----
From: "Cornel Ghiban" <ungreen at gmail.com><mailto:ungreen at gmail.com>
To: "Rion Dooley" <dooley at tacc.utexas.edu><mailto:dooley at tacc.utexas.edu>
Cc: "Discussion of iPlant API development" <iplant-api-dev at iplantcollaborative.org><mailto:iplant-api-dev at iplantcollaborative.org>
Subject: [Iplant-api-dev] Agave API changes
Date: Wed, Dec 11, 2013 8:43 PM

Hi all,

I was working on migrating my API wrapper to v2 and noticed the endpoint for listing files is now /files/2.0/listings instead of /v2/files/.

Is this the case for all the other end points (jobs, apps, etc)?

Thanks,
Cornel


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20131212/3495d9a7/attachment.html