Proposed new charm store API

[Gustavo Niemeyer]

On Wed, Jul 9, 2014 at 12:52 PM, roger peppe <rogpeppe at gmail.com> wrote:
> On 9 July 2014 16:24, Aaron Bentley <aaron.bentley at canonical.com> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 14-07-09 11:16 AM, roger peppe wrote:
>>> If we need to provide backward compatibility, we could do that in a
>>> separate name space without changing the proposed API.
>>
>> The existing charm-events endpoint requires a revision-id, so it will
>> not work when uploads are done directly instead of being ingested from
>> a VCS.  Similarly, the "digest" field of charm-info would not be possible.

The information is already optional in the charm-events API, and
making the field optional if indeed it makes sense to not have it is
trivial.

> Indeed, it's not clear how some current charm store features would
> fit into a charm store that does not do any of its own ingestion,
> but instead relies on clients to upload their own charms.
>
> This is an area we need to resolve more clearly.

Indeed, the problems in doing so ought be well understood if there is
a plan to replace it for precisely that reason.


gustavo @ http://niemeyer.net