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

[Clint Byrum]

Excerpts from Gustavo Niemeyer's message of Fri Mar 23 11:51:28 -0700 2012:
> 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?
> 

Indeed, no immediate changes are necessary to get the policy in place,
and we can work on having a better UX for password configs later.

Possibly Related bugs:

https://bugs.launchpad.net/juju/+bug/922900
https://bugs.launchpad.net/juju/+bug/862418