Policy suggestion for charm store regarding config.yaml and passwords...

[Gustavo Niemeyer]

On Thu, Mar 22, 2012 at 20:09, Clint Byrum <clint at ubuntu.com> wrote:
> Another way to go is to just have the ability to define functions as
> defaults and have a 'password(length)' function available. This way on
> deploy, if no value was specified, it would be generated, and available as
> 'juju get myservice password' immediately after an automated deployment
> script runs.
>
> For now, the charm should probably just use juju-log to inform the user
> about it, and they can extract it from debug-log or the charm log if
> need be. Another option is to error out with a message informing the
> user that this setting is required.

Those are both good ideas. We do need a channel of communication of
relevant details from charm to admin. "juju get" might not be it, as
the converse "juju set" is targeting configuration of the charm, which
is a slightly different class of problems. Your workaround sounds
great for now. Can we put that issue back on the table once we have
time to breath again?

-- 
Gustavo Niemeyer
http://niemeyer.net
http://niemeyer.net/plus
http://niemeyer.net/twitter
http://niemeyer.net/blog

-- I'm not absolutely sure of anything.