Fwd: handling private user data

Juan Negron negronjl at xtremeghost.com
Sat Sep 15 17:12:19 UTC 2012


Forgot to add the list to the reply ... doing that now


Thanks,

Juan



---------- Forwarded message ----------
From: Juan Negron <negronjl at xtremeghost.com>
Date: Sat, Sep 15, 2012 at 10:11 AM
Subject: Re: handling private user data
To: Ricardo Kirkner <ricardo.kirkner at canonical.com>


Hi Ricardo:

The way you describe in your question ( having a config option that points
to a repository, file server, etc. ) seems reasonable to me.

Another way would be to have a directory  in the charm itself where you can
put said files so the charm can use them.  This would require the
devops/user to download the charm before deploying it.  The latter option
could be considered a bit more paranoid as it would require you to download
the charm, adding the necessary files to a predetermined directory and
deploy ( from your local computer ).


Thanks,

Juan



On Sat, Sep 15, 2012 at 7:19 AM, Ricardo Kirkner <
ricardo.kirkner at canonical.com> wrote:

> Hi,
>
> I'm trying to write a charm so that I can completely automate my dev
> environment (and potentially start working from the cloud, or at least
> have everything I need one juju deploy away).
>
> This involves certain aspects which are really easy to do like:
>
> - install packages
> - clone branches
> - include configuration files
>
> However, that last item is only easy if the configuration files don't
> include any sensitive data (as long as you want to keep the charm
> opensource, which is my case).
>
> The problem I find is that I want to include sensitive information like
>
> - ssh keys
> - gpg keys
> - password files
>
> which for obvious reasons I cannot/will not host on a public repository.
>
> So the question is, how can handle private user data when deploying a
> charm?
>
> I currently keep a repository for these files in a usb pendrive, and my
> natural thinking was adding a config option to my charm to set the
> location to that repository and then have the charm somehow push/clone
> that repository into the unit, but I haven't found any way of doing this.
>
>
> Any ideas on how to solve this, or work around it until there is an
> official solution are really welcome :)
>
> thanks
> Ricardo
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20120915/6e53e5a1/attachment.html>


More information about the Juju mailing list