Why can he not upload the resources? We have several mechanisms in place to allow for gating charms based on things like "accepting terms", and a general policy that "juju deploy SOFTWARE" should actually get you SOFTWARE running in a functional manner. Telling people "do this deploy, but then go get the real functional by visiting these websites" is not a good user experience, so we're unlikely to try and polish things like "don't allow people to see that there are 0 byte resources".
John =:-> On Fri, Dec 2, 2016 at 2:48 PM, Konstantinos Tsakalozos < kos.tsakalo...@canonical.com> wrote: > Hi all, > > Ionut Balutoiu (in cc) would like to use the resources mechanism but he > cannot upload the actual resources to accompany the charm. Instead he will > prompt the users to attach their own binaries during deployment. To serve > this use case Ionut can upload a dummy zero-sized binary to the store and > use its size to detect if the user has provided his own binary. This works > but has a side effect, the dummy binaries are available for downloading > from the charm's page. Is there a way to hide the resources from the > charm's readme page? is there a more elegant way to serve this use-case? > > Thanks, > Konstantinos > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/juju > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
