Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: error (nike.apache.org: local policy)
Date: Fri, 23 Aug 2013 09:10:44 -0400
From: Chip Childers <chip.childers@sungard.com>
To: dev@cloudstack.apache.org
Subject: Re: registerSSHKeyPair
Message-ID: <20130823131044.GG3154@USLT-205755.sungardas.corp>
References: <DFEAA7E9-4FAB-42D8-8322-B98E22113BBF@gmail.com>
 <CAAt5S3YdFW=UcA7=rDvUbHrY9zxxvGOEKs5ue3Pzan=tBQhRKg@mail.gmail.com>
 <175BDDB1-01DA-4382-BDAD-7D402229C43D@gmail.com>
 <7C985EF4-6714-4883-ACDA-A0AD34A29899@citrix.com>
 <8E6E279D-7ADE-4A34-A74F-5201734CEC8F@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8E6E279D-7ADE-4A34-A74F-5201734CEC8F@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Thu, Aug 22, 2013 at 08:33:42AM -0400, Sebastien Goasguen wrote:
> 
> On Aug 22, 2013, at 7:57 AM, Harikrishna Patnala <harikrishna.patnala@citrix.com> wrote:
> 
> > We generate docs based on the response object. Since we use the same response object for create/register ssh key pair APIs, doc shows same return values.
> > We follow this for all API responses. Say list virtual machine API response does not include all the fields that are in api doc.
> > 
> 
> I understand, but that's a case where it's misleading. Maybe the response objects should not be the same after all.

+1 - this is another example of where the CS API leaks implementation
details all over the place, in this case manifested as a documentation
issue.