Hello John, I’m aware that there is a way to prompt users to accept EULA on deploy time, but I’m worried about the fact the resources are downloadable from the charm home page. I’m not sure this is fine as I think we redistribute the software this way and there are EULA’s that might not allow this. Uploading a zero bytes resource and instructing the users in README how to pass the real resources, should do the work, but it’s just a workaround. I would’ve liked to be able to release/publish a charm without specifying any resource and have them grayed out on the portal, the way they are right now before publishing. This is an example of a charm that I want to publish and I don’t want any resources uploaded on the charm store: https://jujucharms.com/u/cloudbaseit/azure-service-fabric/8
Regards, Ionut From: juju-boun...@lists.ubuntu.com [mailto:juju-boun...@lists.ubuntu.com] On Behalf Of John Meinel Sent: Friday, December 2, 2016 15:19 To: Konstantinos Tsakalozos <kos.tsakalo...@canonical.com> Cc: juju <juju@lists.ubuntu.com> Subject: Re: Hide resources from showing on the store 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<mailto: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<mailto: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
