charm store: serve metadata and config?

[Gustavo Niemeyer]

On Wed, May 23, 2012 at 7:38 AM, William Reade
<william.reade at canonical.com> wrote:
> On Mon, 2012-05-21 at 14:23 -0300, Gustavo Niemeyer wrote:
>> Sounds good. As a recommendation-less heads up, let's watch out for
>> what's the cheapest way to reach parity. This isn't the time to dive
>> into extensive research/experimentation to attempt to change the way
>> things work. If we can change it cheaply, that's nice, but if there's
>> risk of it becoming a two-months task just to figure the best way
>> possible to make it work, let's move on with what we already did
>> before.
>
> That risk surely exists :). I'm entirely comfortable with downloading
> them to a local cache (as before); but just using the charm store
> bundleUrl where available (and hence skipping the upload to provider
> storage).

This breaks the deployment of local charms. Let's please resist the
temptation of screwing up what we know works in Python unless we have
a very clear plan.


gustavo @ http://niemeyer.net