Planning for Juju 2.2 (16.10 timeframe)

[Tom Barber]

Yeah, I guess that would be a good solution for sample data and stuff.
Doesn't work for user defined bits and pieces though. For actions we
current "cat" the content into a parameter, but of course that doesn't work
for everything, and really really sucks when you try and cat unescaped JSON
into it. But for users who want to deploy their own content to services,
personally I think it would just be cleaner to allow a file type in an
action for people to pass in.

--------------

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart
<http://kickstarter.com/projects/2117053714/saiku-reporting-interactive-report-designer/>
goal, but you can always help by sponsoring the project
<http://www.meteorite.bi/products/saiku/sponsorship>)

On 18 March 2016 at 16:44, Eric Snow <eric.snow at canonical.com> wrote:

> On Fri, Mar 18, 2016 at 8:57 AM, Tom Barber <tom at analytical-labs.com>
> wrote:
> > c) upload files with actions. Currently for some things I need to pass in
> > some files then trigger an action on the unit upon that file. It would be
> > good to say path=/tmp/myfile.xyz and have the action upload that to a
> place
> > you define.
>
> Have you taken a look at resources in the upcoming 2.0?  You define
> resources in your charm metadata and use "juju attach" to upload them
> to the controller (e.g. "juju attach my-service/0
> my-resource=/tmp/myfile.xyz"). *  Then charms can use the
> "resource-get" hook command to download the resource file from the
> controller.  "resource-get" returns the path where the downloaded file
> was saved.
>
> -eric
>
>
> * You will also upload the resources to the charm store for charm store
> charms.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20160318/d2d5099a/attachment.html>