Bug 680503

Summary: RFE: Unified API error message format
Product: [Retired] Pulp Reporter: Mike McCune <mmccune>
Component: z_otherAssignee: Sayli Karmarkar <skarmark>
Status: CLOSED CURRENTRELEASE QA Contact: Preethi Thomas <pthomas>
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: cperry, skarmark
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
: 680520 (view as bug list) Environment:
Last Closed: 2011-08-16 12:10:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 673021, 680520, 684061    

Description Mike McCune 2011-02-25 18:18:32 UTC 
Requesting errors from Pulp's REST API be returned in JSON format in a standardized manner.  Most expected errors return a body message:

$ curl -k -u admin:admin https://localhost/pulp/api/repositories/kgems-1234777/sync/ed50d051-4108-11e0-89b7-00219b3b5088/

"No sync with id ed50d051-4108-11e0-89b7-00219b3b5088 found"

but ideally if there are expected errors we could use a JSON message format:

    {error-name: "sync-not-found", message: "No sync with id ed50d051-4108-11e0-89b7-00219b3b5088 found"}

or something similar.  This would make handing exceptions much easier from a caller's perspective.
Comment 1 Preethi Thomas 2011-08-16 12:10:47 UTC 
Closing with Community Release 15

pulp-0.0.223-4.
Comment 2 Preethi Thomas 2011-08-16 12:22:36 UTC 
Closing with Community Release 15

pulp-0.0.223-4.