Charming with Resources

[Charles Butler]

TL;DR - would it be helpful to just initialize every resource stream, at
index 0, a zero byte resource?  This aids users who are publishing charms
with copyrighted bins, or proprietary components. And give an immediately
publishable resource for streams.


It occurred to me this week while we were revving through the kubernetes
publication process, that on initial publish its best to have zero byte
resources at index 0. So its easy to remember - "man which resource was the
zero byte one?" it just corresponds to 0.

Instead of having users touch, gzip, etc a null resource, would it be
feasible to make the charm store have this convention by default? Every
charm that declares a resource, that resource, in turn gets a resource-0
allocated for zero byte, freeing the publisher of the charm to use the
provided null resource?  seems like a better UX than asking the user to
jump through hoops of say:

touch null && gzip null && charm attach mycharm big-resource=null.gz

There's likely a reason we didn't do this by default and I'm interested in
hearing it. However, I'm more interested in finding out if we can
streamline resource publication for our vendors and community.

All the best,

Charles
-- 
Juju Charmer
Canonical Group Ltd.
Ubuntu - Linux for human beings | www.ubuntu.com
Juju - The fastest way to model your application | www.jujucharms.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160929/221bf019/attachment.html>